If these sorts of devices were to be developed at a later time I would envisage that it would provide only scan and diag functionality. Basically a more graphical and enriched experiance than is provided on the FlashScan V2 standalone today. I can't see the Tune Tool functionality ever being ported to a device like these.
On the device debate... I'll start by saying that I personally have and use an iPhone, but that it is the ONLY Apple product I have ever owned and that I am by no stretch of the imagination an Apple "fan boy".
I have recently been an Android owner as well (I bought 2 Samsung Galaxy S phones). I owned them for less than a month before selling them and getting 2 iPhone 4's (had annoyingly already sold our iPhone 3GS'). Anyway I was highly annoyed by the Android experience, not fore reasons of Android necessarily. The Android platform I think has to resolve these issues before it will become a compelling platform:
- Android 2.2 was released back in May 2010 and it was only starting to be made available to the Samsung Galaxy S platform (one of the first to offer an upgrade from 2. I believe). This was basically just in time for the 23 Android version to be released. Be each manufacturer taking a fork of Android at a point in time and then messing with the interface and applications on their specific device serves to slow down the whole release cycle to the customer. I think Android should prohibit device manufacturers modifying or augmenting functionality to any large degree so that the updates and functionality improvements are available to ALL customers promptly. This is essentially what is true from customers of the actual Google Nexus One, and probably the Google Nexus S also.
- Every single mobile carrier that provided and Android device seems to have an entirely customised firmware. This is typically so that they can brand the startup screen and probably more importantly include APN details for the device to access the internet etc, as well and SMS and messaging details. In addition to the above this creates a massive overhead on the device manufacturer and also serves to slow down any release due to inordinate testing and validation. I actually bricked one of these expensive phones while trying to be clever and get to a 2.2 firmware before it was oficially available from my carrier. Fortunately it was able to be recovered
- Lastly. I had a number of applications that I downloaded or purchased for the Android which were common with applications I used or bought for the iPhone. What I found is that the user experience and interface on the Android applications was quite variable vs. the Android standard apps. Things like the contacts list in VoIP softphones for instance appeared and functioned differently. By contrast what I'd considered to be the communist approach of Apples approval of all apps in the App Store actually serves to provide quality apps that for the most part look and feel consistent. Perhaps the included APIs are just better at this time.
Anyway, overall I was personally pretty surprised how poor and disjointed the Android experience was right now. I have no doubt it will get better, but I really think it should be ahead of where it is already at version 2.3. Take for instance the much publicised issues with SMS messages going to incorrect contacts, that's seriously bad and the bug has been around for months