2 ms·
You can still do internal dev, but it's a hell of a lot less convenient. You buy multiple 99 dollar dev licenses and do adhoc builds, and have to provide new pr
by gte910h 16y ago
You can still do internal dev, but it's a hell of a lot less convenient. You buy multiple 99 dollar dev licenses and do adhoc builds, and have to provide new provisioning profiles every 3 months.
Not perfect, but still possible.
Android, per se, doesn't exist. 3 Android platforms do, 1.5, 1.6 and 2.x. The issue with android even in the companies that have working stores and payment systems, is horrible horrible fragmentation. Hopefully they do something to fix this, but it honestly feels like the Android team at google is all engineers and no businesspeople negotiating a solution to this HUGE problem for that "platform" which is really 3 platforms.
It is like if windows had 30% on windows 3.1, 30% on windows 98 and 35% on windows XP SP2 and the other 5 percent on all sorts of things currently. There is that big of a gulf between the different OS versions when trying to program for it (which I do).
I want android to succeed. It's just not here yet.
- hga 16y agoI guess my point here is that the things that I cited will very possibly give Android time to succeed. It might not generally succeed, e.g. Apple may be able to carve out a long term and large niche of the market, but it seems to me that they're near totally excluding themselves from many important ones. E.g. a lot of people talk about the using the iPad in health care. That strikes me as a non-starter unless Apple is able to change that market ... which they just might be able to do by directly working with a few 3rd parties. But not as the market stands today. There's a very good chance you're right in your near term 3 year prediction ... but I could see things swinging faster, although not much faster. 2 years at minimum.
- gte910h 16y agoI think things will go one way or the other with this: The Apple "You can't innovate on the small scale" bias caused by their dev license policies might actually help fight medical record fragmentation. I can see a couple "trusted clients" talking to a few "standard EMR formats" on standard compliant servers finally taking hold if the device captivates doctors. Additionally, the iPad works just fine with web software that doesn't use onmouseover. Lots of hospitals have much of their software on internal websites. Then again, medical software always has been ultrafragmented, and perhaps it will stay that way, in which case android will likely be the implementation platform (or jailbroken iPads)