Apple’s initial iPhone application model (build a decent website) is brilliant. Websites are easily the fastest, most compatible, most maintainable, most popular, way to create software applications. Once Apple supported adding specific website’s to the icons on the iPhone’s home screen, you’ve got the equivalent of applications on the Palm Treo – with internet access required, sure.
Doesn’t (or shouldn’t) this model cover 97% of all software?
The alternative is learning Objective-C, the development language in OS X and the amazingly popular GNUStep. Um. While not exactly wide reaching, this should increase the demand for ObjC developers.
For the commitment to ObjC, what to you get?
Some deeper ties into the iPhone’s hardware capabilities and iTunes as only distribution method.
In a client meeting earlier this week the team mentioned how the project needed to be available on mobile devices for internal use.
This brought to mind the Symbol barcode scanner running Palm’s OS and the handheld devices package delivery people at UPS and FedEx use.
Could they be replaced with an iPhone?
Scanning an object’s barcode and manipulating data about it by multi-touch is a very compelling vision – whether on sales floor or in the warehouse.
On the flip side, I have a hard time imaging signing for a package on an iPhone…or enterprises IT departments agreeing to push out updates to a iPhone-native app via iTunes.