1 / 19

MOBILE WEB APPS

MOBILE WEB APPS. Authors : Nicolás Serrano, Josune Hernantes and Gorka Gallardo University of Navarra’s School of Enginering. Elif Nurdan İlgar. Applications. In the past -> Desktop applications Now -> Mobile applications Different types of web apps with different options.

kaili
Download Presentation

MOBILE WEB APPS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MOBILE WEB APPS Authors: Nicolás Serrano, JosuneHernantesand Gorka Gallardo University of Navarra’s School of Enginering Elif Nurdan İlgar

  2. Applications • Inthepast-> Desktop applications • Now-> Mobile applications • Differenttypes of web appswithdifferentoptions

  3. Mobile Web Applications • Different meanings 1- Web appsthatdesigned to appear correctly on a mobile device.Ex: mobile sites 2- Native app built for specific mobile OS thatconnectsto Web tosendandreceive data. Ex: chromeappforiphone

  4. Mobile Web Applications • Standard Web Apps: • Designedtowork on computerbrowsers • Also 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

  5. Mobile Web Applications • Responsive Web: • Single code source that changes design up to device features using CSS files. • Usefull for tablets, game consoles, televisions ...etc • Ex: http://thehaberdasfox.com

  6. Mobile Web Applications • Mobile Web: • Specific web site for mobile devices • Uses user interface controls (buttons, selectors, text boxes…etc) similar to a native app • Ex: http://www.ziraatbankasi.com.tr

  7. Mobile Web Applications • HybridApps: • Mobile web apppackedinto a nativeapp • Install from app store • May accesstodevice’sfeatures • But developedusingsametoolswith web app. Ex: HTML5, CSS, javascript…etc

  8. Mobile Web Applications • NativeApps: • Specificto mobile OS • May useall of thefeatures of thedevice • Developedusingprovider’slanguageandframework. Ex; • xcodewithobjective c foriOS • Eclipsewithjavaforandroid • Ex: facebook app for ios

  9. Techical Considerations • 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 peripheral • native or hybrid apps • better • can provide direct access to device features

  10. 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

  11. 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 resources • always must be tested by using prototip or simular existing apps

  12. Techical Considerations • Upgrade: • Native -> • Can’t force users to upgrade • Simultaneously serving different versions • Same for hybrid if the code is in the local part of the app

  13. Non Techical Considerations • Distribution: • Discoverability issues: • Users can’t find the app outside the app store • Hybrid or native apps are preferable • Platform store handle distribution problems • However, app store might have thousands of app competing for user attention

  14. 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 gateway • Platform owners get significant amount of the revenue (Ex: ios -> %30)

  15. Frameworks • Native: • Cross-platform • Just one codebase for all devices • Selection of the platform up to our prefered development language (Ex: javascript, rubby…) • Hybrid: • Phone gap • Predominant technology • HTML5 frameworks • Sench mobile packaging • Supports only iOS or android

  16. Frameworks • HTML5: • Try each frameworks that best fits our development • Plenty of options -> • Bigger framework codebase • Affects performance and bandwith consumption • To overcome this issue -> • JQuery Mobile can select just the necessary modules for a project

More Related