- Requires full rewrite in Windows 8/WinRT – not so good for mobility firms
- Asynchronous model – awfully frustrating -try downloading a file and you’ll see
- No direct access to data outside of the OS – hair loss, anyone?
- The new Touch UI – another horror story. Even Microsoft agrees
- Microsoft’s app store rules – Berlin wall
- No tablet hardware – honestly?
- Developers cannot just recompile old 32-bit apps to fit iOS7 64-bit OS
- Too many overlays and transparencies
- Complicated mobile app development process and timelines
- User interface shock value – another learning curve for users
- Version 1.0 out in 2008; Cupcake, Donut and Éclair also out within the year. What’s the hurry, Google?
- Two version updates within a year seems the Android standard
- Mobile app development for Jelly Bean put on hold, awaiting KitKat’s release
KitKat’s going to take some getting used to, and here’s keeping fingers crossed that Google doesn’t release another OS version in 2013. It’s not all gloom and doom, though. Google’s ‘Google Experience’ will certainly make it easier for older Android versions to use Google Play. And iOS7 does bring smarter multi-tasking, better voice control and more user-friendliness.
The new BYOD trend is motiving firms to build their own inhouse apps. Now, with multiple OS in the market, each updating several times a year, how feasible is it to devote resources to developing apps inhouse? What’s your take on all of this?
So, eager to learn why your business MUST take notice of Mobility ? Or want to decide which app is a right fit for your business? Download your choice !