Here’s a quick rundown of the iPhone 5C and 5S launch from my Twitter liveblog:
Where Apple is leading:
- The 5S is running on a new, 64 bit A7 processor with a 64 bit version of iOS7.
- The 5S is twice as fast as the iPhone 5 and supports Open GL/ES for games with desktop-level graphics performance.
Where Apple is playing catchup:
- The CoreMotion API is a good idea and I had a unified Motion API on Windows Phone “Mango” a couple of years ago.
- Using the Touch ID fingerprint reader to login to the device and make iTunes purchases is a good idea and I had a fingerprint reader on my Compaq iPAQ over a decade ago.
- Using a bigger sensor, aperature, and pixels for the new camera helps them catch up to the innovations found in the HTC One but they’re still light years away from the innovations found in the Nokia Lumia 1020.
- Purchasers of new iOS devices get all iWorks apps for free just like purchasers of Windows Phones have always gotten Microsoft Office for free.
- As mentioned everywhere on the Internet, the iOS7 UI tries to cobble together the best of Windows Phone and Android Jelly Bean while eliminating skeuomorphism.
- The colorful polycarbonate iPhone 5C devices mimic the colorful polycarbonate Nokia Lumia devices.
Where Apple missed:
- At $549, the iPhone 5C isn’t even close to being inexpensive enough to make a dent in the developing world the way Android & Nokia has. When I can buy a Nokia Lumia 520 Windows Phone at Walmart off-contract for only $124, the value prop for the $549 iPhone 5C evaporates. Apple shares have tanked as shareholders didn’t get the low cost device they demanded to boost the iPhone’s declining market share.
- No improvement in battery life.
Is the iPhone 5S a decent upgrade to the iPhone 5? Absolutely. Is it the mind-blowing example of design and technology that we’ve come to expect from Apple? Absolutely not.
I was surprised to hear Todd Bishop over at GeekWire say the iPhone is the IBM of smartphones. I’m sure that’s the comparison Apple was looking for…
Is your SOA infrastructure ready for mobile devices & unreliable wireless networks? It’s time to convert SOAP to REST, XML to JSON, uncompressed to compressed, uncached to cached. It’s time for MSOA.
I’m sure you’re inundated with a steady stream of news and information about the Bring Your Own Device (BYOD) component of the Consumerization of IT (CoIT) phenomenon on a weekly basis. Yes, a good percentage of your employees are walking into the office with a wide range of smartphones and tablets every day and they want to be productive. Let me share just a few ways you can facilitate a positive outcome for your employees via completely ‘invisible’ means.
The first is enabling Exchange Active Sync (EAS) to securely provide your employees with email, contacts, calandar, tasks and ‘light’ mobile device management (MDM). Virtually every smartphone and tablet on the planet comes with the EAS client bits as a standard component of the mobile operating system. Whether you’re running Exchange Server in your own data center or in the cloud via Office 365, your employees can quickly and easily become connected with their coworkers. Oh, and you get mobile policies like password enforcement, device encryption, remote wipe and others for free.
The next thing you can do is use a reverse-proxy server or appliance on the edge of your network to securely publish web services and web sites out to the Internet. Without having to fumble around configuring and pre-connecting a VPN tunnel, your mobile employees can access the corporate information they need just as easily as they do when connecting to other resources on the web. Those services and sites will be wrapped in SSL and require appropriate network credentials in order to access them. If you’re currently publishing Exchange Active Sync out to the Internet today, then you probably already have this capability in place via server technologies like ISA, UAG, and others.
The last thing I want to focus on are those web services and web sites you’ll be securely publishing to the Internet for mobile consumption. It’s important that they be efficient over slow wireless networks and work with any mobile device or web browser. You web service wire protocol needs to be REST instead of SOAP and your data must be serialized with JSON instead of XML. Mobile web users must either be directed to a mobile version of your site or you should employ Responsive Design principles to provide the best experience. Those web apps must use the HTML5 Application Cache so they can work offline as well as IndexedDB or Web Storage to store data on the device just like a native app.
These are just a few things you can do to deliver ‘quick wins’ for the employees at your company without compromising security.