The document compares native mobile apps versus mobile web apps. It discusses their differences in terms of user interface, development, capabilities, monetization, delivery method, versioning, strengths, and weaknesses. Native apps have full access to device features but are more expensive to develop and maintain across platforms. Web apps are cheaper but have limited device access and performance issues. The document also provides questions to consider when deciding between the two options for building a mobile app.

1. Mobile web applications production for business
GBG Alex 09 Nov, 2012

2. Native vs. web
● Business View
● User interface
● Development
● Capabilities
● Monetization
● Method of delivery
● Versioning of the app
● Strengths
● Weaknesses

3. User Interface
● "Almost" the same look and feel :)

4. Development
Native Web
Each OS requires its own development Doesn't require anything to run but a
process, native language and SDK browser :)
Choose your favorite language :)
Programmers availability, salaries.
Developing apps for deployment on multiple mobile OS platforms and web browsers
(e.g. PhoneGap, Sencha Touch 2, Appcelerator Titanium, etc.)

5. Capabilities
Native Web
Can interface with the device’s native Mobile web apps can access a limited
features, information and hardware amount of the device’s native features and
(camera, accelerometer, etc.) information (orientation, geolocation,
media, etc.)

6. Monetization
Native Web
Mobile-specific ad platforms such as Mobile web apps can monetize through
AdMob (though there can be restrictions site advertisement and subscription fees
set by the mobile device’s manufacturer)
Developers have the ability to charge a Charging users to use the mobile web app
download price and app stores will typically requires you to set up your own paywall or
handle the payment process (in exchange subscription-based system
for a percentage of sales)

7. Delivery Method
Native Web
Stand-alone installation must be manually No downloads nor installations are
downloaded from a store or market required
Must be manually updated Updates are made to the web server, no
user intervention
Versioning
User may ignore the update resulting Same version all the time :)
different users running different versions

8. Strength
Native Web
Perform faster Only one common base
Store or market can assure quality and Can be released in any form and any time,
safety no one has to prove it
Tools and support almost provideyd by the You can provide tools and support using a
manufacturer Responsive Design

9. Weaknesses
Native Web
Expensive development especially if you'll Supporting multiple systems may raise the
support multiple systems cost but still will be better
Harder to maintain Can't access all device features
Launch delay due to approval process Harder to find

10. Build Mobile Apps Questions
● Do I need to use any special device features
(i.e., camera, the camera’s flash,
accelerometer, etc.)?
● What’s my budget?
● Online, semi-online or offline?
● Do I need to target all mobile devices?
● What programming languages do I already
know?
● How important is speed and performance?
● How will this app be monetized effectively?