With built-in cameras, flash/light, accelerometer, GPS, M7 coprocessor, Bluetooth, compass, audio & video recording, etc., devices today sometimes need a UX that’s far beyond filling out fields in a form. Not all apps, certainly, but sometimes it’s best to completely rethink the business problem rather than port an existing web solution.

Clearly these are consumer use cases, but it just takes a little imagination to think about how these sensors could be put to use in an LOB app. Can bar codes be acquired via the camera? Can data be acquired via Bluetooth? Would audio input be useful? Can the user’s location data and orientation be derived automatically?

http://www.apple.com/iphone-5s/powerful/

Last year at about this time, Apple announced that new apps and app updates would need to support the larger screen of the iPhone 5, or they wouldn’t be accepted into the store.

As of Feb 1, 2014, Apple did much the same for iOS 7 support.

When will the 64-bit decree come down? Or, at the very least, when will Apple start flagging 64-bit support in the App Store?

At Build, Microsoft announced the concept of universal apps that will run on Windows Phone 8.1 and Windows 8.1 and Xbox One. With a unified app store to come, architects, UX designers, and developers will need to think about mobility simply as an alternative interface, not reduced functionality.

Your app’s views will differ on a Windows phone, tablet, PC, and Xbox One, but your data model and business logic should be identical.

My talk at Twin Cities Mobile March came before Build, so it’s very iOS specific, but the same ideas apply: