HTML and CSS Reference
In-Depth Information
What happens though if your app utilizes device-specific information such as offline
storage, GPS, notifications, or accelerometers, along with WebSockets? You need a
more native implementation in a language other than HTML and JavaScript. W3C is
defining some specifications that will let the client access hardware such as camera,
GPS, and accelerometer. However, only a minority of modern web browsers cur-
rently support such specifications. At the time of writing, a native approach is the way
to go, though the client-side future seems way more interesting! iOS uses Objective-
C, Android uses Java, and Windows Phone uses C#. If you think that your mobile
use-case scenario does not utilize any of the smartphone goodies, feel free to go
with the browser-based app. If native functionality is required, then a native solution
is necessary. That's exactly what are we going to build in this chapter!
In order to develop a smartphone app, you need to install the development tools and
SDKs of your preferred target. The philosophy behind the examples we'll demon-
strate is fundamentally the same in the three major mobile operating systems, that
is, iOS, Android, and Windows.
If you do not already have a mobile SDK installed, here is where you can pick one
(they are all free):
Platform Targets
iPhone, iPad
Android Android phones & tablets
Windows Windows Phone, Windows
8 devel-
Search WWH ::

Custom Search