- This topic has 150 replies, 25 voices, and was last updated 14 years, 1 month ago by
.
-
Posts
-
Re: The Fault Code Guide
We have got it working, sorta, on Android but it isn’t ready for release as yet and one of the devs is on holiday ATM just to compound it. Converting for Android has however involved a world of hurt in database handling among other things as the plan is to be able to update the app on the fly.
What that means is that, as more codes are discovered, we can add them and update as they become available.
That also introduces several challenges into the mix as the app has to talk back to a repository for information to update itself.
Then of course we have to consider being able to pull information from other sources, deliver some information when it is needed rather than hogging the available memory on the device…
If only it were simple. :rolls:
If it were so simple, I guess someone would have done it already, the fact that they haven’t tells you a lot. Sure, you can do a single brand thing as the likes of LG have done or tried but, not much use if you’re not attending and LG machine.
It’s a huge big stinky pile of learning curve.
Then, to top that, I want it to do so, so much more because the technology will allow it to do it if you use a little imagination but that has to come in incremental steps or it would languish as vapourware forever.
Plus, we have this little skunkworks project running known as Rapport that needs sorting as well and we have to consider that as well.
On the upside however, we are making headway with it all and expect a fresh release of Rapport this week ahead of the meeting on Friday. There’s some really cool stuff in it that allows us to progress that and some even cooler stuff to come that’s already in development that I may or, may not, demo on Friday as I haven’t made my mind up on it yet and I need the internet to do it.
In other news, we’ve just been okay’d for a second Knowledge Transfer Partnership (KTP) in partnership with the University of West Scotland (UWS) to work on mobile apps for you lot. Which will please Jim and his Windows phone as that’s just blipped on my radar given the patent wars ongoing in the tech world.
One of the big issues with all this sort of thing is that, if we release it and it isn’t as good as we want that’s fine and most people understand that we really are fighting on many fronts given that we don’t have an unlimited bucket of resources like Google et all to play with. But, at the same time, you draw criticism which means that we try to get it as right as we can before release, even if we know it isn’t 100{e5d1b7155a01ef1f3b9c9968eaba33524ee81600d00d4be2b4d93ac2e58cec2d} the way we want it.
I welcome the criticism TBH so long as it’s constructive as it helps us make it better where it’s justified. Plus if we’re being a bunch of muppets then we should be told that we are. No harm, no foul.
But do be aware just how limited we are, even with the backing of UWS, KTP and so on as there is a development team of two for the actual logic to make this stuff work, me and Sudeep. Behind that there’s two other coders, one on Android development full time and the other on dbase coding for Rapport. In other words, we are working with limited resources which most of you will be able to relate to as you mostly run your own businesses.
However I’ll probably get dragged into a conversation about all of this and have a chance to explain more on it on Friday at the meeting for those that are there as, in all honesty and with no disrespect, I simply do not have the time to type out all that’s going on with apps and Rapport in the forums in advance. I usually have a chance to do it later, but not always and we’re keeping up with an industry that seems to move at faster than light speeds, most unlike ours that moves at a leisurely glacial pace. On a slow day.
K.
Re: The Fault Code Guide
Hi K
Sorry for nagging but is any release date on the android fault code app yet.
Thanks
Mr Phil
Re: The Fault Code Guide
I have just been reading about this forthcoming android release, and I must say it comes as good news to me.
I have an android phone (Samsung S2) that I take with me on jobs. Often I need to look up a fault code and find when I view “UK Whitegoods fault code guide 2011 free.pdf” through Mantano Reader Premium I get a big black bar right through the middle of the page. This obliterates information I want to read.
I am pretty sure it’s the “UK Whitegoods” watermark that’s causing this. Anyone any comments as to how to get around this?
Thanks in advance,
Alan.Re: The Fault Code Guide
trusted wrote:I am pretty sure it’s the “UK Whitegoods” watermark that’s causing this. Anyone any comments as to how to get around this?
Yes, download the app “ThinkFree Office Mobile Viewer” (which is FREE) or the better pay up version (£5.50). 😉
Re: The Fault Code Guide
We are going through a major update in iOS, It is in status waiting for review. Will update you once it is approved.
Re: The Fault Code Guide
downloaded it it is obviously a trial version it offers me to buy the full version but there is no cost. how much is it
- You must be logged in to reply to this topic.