Authors: Nicolás Serrano, Josune Hernantes and Gorka

GallardoUniversity of Navarra’s School of Enginering

MOBILE WEB APPS

Elif Nurdan İlgar

In the past -> Desktop applicationsNow -> Mobile applications

Different types of web apps with different options

Applications

Different meanings1- Web apps that designed to appear correctly on a mobile device. Ex: mobile sites2- Native app built for specific mobile OS that connects to Web to send and receive data. Ex: chrome app for iphone

Mobile Web Applications

Standard Web Apps: Designed to work on computer browsersAlso works on mobile device’s browsers if they

don’t need specific browser features such as Adobe Flash…etc

Ex: http://kikencere.gsu.edu.tr

Mobile Web Applications

Responsive Web:Single code source that changes design up to

device features using CSS files.Usefull for tablets, game consoles,

televisions ...etcEx: http://thehaberdasfox.com

Mobile Web Applications

Mobile Web:Specific web site for mobile devicesUses user interface controls (buttons,

selectors, text boxes…etc) similar to a native app

Ex: http://www.ziraatbankasi.com.tr

Mobile Web Applications

Hybrid Apps:Mobile web app packed into a native appInstall from app storeMay access to device’s featuresBut developed using same tools with web app.

Ex: HTML5, CSS, javascript…etc

Mobile Web Applications

Native Apps:Specific to mobile OSMay use all of the features of the deviceDeveloped using provider’s language and

framework. Ex; xcode with objective c for iOSEclipse with java for android

Ex: facebook app for ios

Mobile Web Applications

Platforms and version support:If the goal is app with multiple platform

support -> hybrid or mobile web

better than native app (native must be developed for each mobile platform)

Device capabilities:If app needs access to camera, file system or a

peripheralnative or hybrid apps

bettercan provide direct access to device features

Techical Considerations

User experience:Hybrid->

access to native API cost of nonnative user interface due to Web

technologies involved (HTML5…)Native ->

richer experience with more responsive interface and user interaction

users open app faster and use device specific features

Techical Considerations

Performance:If the user interfaces are graphic – heavy or

require excessive data processing mobile or hybrid apps

have more difficulties to achieve high performance running on the top of additional layers which

consumes computing resourcesalways must be tested by using prototip or simular

existing apps

Techical Considerations

Upgrade:Native ->

Can’t force users to upgradeSimultaneously serving different versionsSame for hybrid if the code is in the local part of

the app

Techical Considerations

Distribution:Discoverability issues:

Users can’t find the app outside the app storeHybrid or native apps are preferable

Platform store handle distribution problemsHowever, app store might have thousands of

app competing for user attention

Non Techical Considerations

Approval Cycle:Fast turnover and continous feedback are

neccessary Hybrid or native ->

Approval process is part of the projectİf no rejection -> total time is minimal

Possibility of having licence for a specific device

Monetization:App store ->

Well-defined payment gatewayPlatform owners get significant amount of the

revenue (Ex: ios -> %30)

Non Techical Considerations

Native:Cross-platform

Just one codebase for all devicesSelection of the platform up to our prefered

development language (Ex: javascript, rubby…)Hybrid:

Phone gapPredominant technologyHTML5 frameworks

Sench mobile packagingSupports only iOS or android

Frameworks

HTML5:Try each frameworks that best fits our

developmentPlenty of options ->

Bigger framework codebaseAffects performance and bandwith consumption

To overcome this issue ->JQuery Mobile can select just the necessary

modules for a project

Frameworks