Web service transition. From desktop to mobile
•
1 like•423 views
The document discusses the technical challenges of transitioning a travel portal from desktop to mobile devices. It notes conceptual differences like smaller screens and touch interfaces on mobile that require a focus on usability, responsiveness and reduced typing. Technically, apps are often developed on desktops but deployed to mobiles, requiring choices between native and hybrid approaches. The main challenges are developing for different contexts and hardware abilities while reusing code across platforms.
Recommended
More Related Content
Viewers also liked
Viewers also liked (15)
Similar to Web service transition. From desktop to mobile
Similar to Web service transition. From desktop to mobile (20)
Recently uploaded
Recently uploaded (20)
Web service transition. From desktop to mobile
- 1. Travel portal — technical transition from desktop to mobile devices
- 3. Problem ? http://bit.ly/PUI6Lk
- 5. Desktop vs. Mobile Context Context sitting on foot concentrated limited attention ● Interaction Interaction mouse touchscreen keyboard sensors Performance Performance high low Screen Screen big small http://bit.ly/PUI6Lk
- 6. Remark resolution + screen size + distance = matters together http://bit.ly/PUI6Lk *image from engadget.com
- 7. What does it mean? usability + responsiveness in highest priority less typing, less buttons more gestures and sensors less noise more information http://bit.ly/PUI6Lk
- 8. Content transition Desktop Mobile Articles Shops Photos Parkings User stories Bus timetbles Weather forecast Border queues http://bit.ly/PUI6Lk
- 10. Main thesis developed on deployed to desktop/server app Desktop Desktop* mobile app Desktop Mobile http://bit.ly/PUI6Lk
- 11. Platforms iOS Objective-C Android Java WP7 C# Go cross-platform? JavaScript + HTML5 http://bit.ly/PUI6Lk *approximatly; based on http://statcounter.com/ data
- 12. native vs. hybrid Native Hybrid + fluently + easy code reuse + full OS integration + fast to develop + immediate updates + A/B testing - difficult to reuse code - doesn't deel native http://bit.ly/PUI6Lk
- 13. Conclusion Conceptual ● different context ● different hardware abilities Technical ● develop on desktop deploy to mobile ● choose right technologies http://bit.ly/PUI6Lk