Web service transition. From desktop to mobile

Travel portal — technical transition from desktop to mobile devices

Already bored?

http://bit.ly/PUI6Lk

Problem

?http://bit.ly/PUI6Lk

Conceptual differences

http://bit.ly/PUI6Lk

Contextsittingconcentrated

●

Desktop vs. Mobile

Contexton footlimited attention

Interactionmousekeyboard

Interactiontouchscreensensors

Screensmall

Screenbig

Performancelow

Performancehigh

http://bit.ly/PUI6Lk

Remark

*image from engadget.com

resolution + screen size + distance = matters together

http://bit.ly/PUI6Lk

usability + responsiveness in highest priority

What does it mean?

less typing, less buttonsmore gestures and sensors

less noisemore information

http://bit.ly/PUI6Lk

DesktopArticlesPhotosUser storiesWeather forecast

Content transition

MobileShopsParkingsBus timetblesBorder queues

http://bit.ly/PUI6Lk

Technical differences

http://bit.ly/PUI6Lk

developed on deployed to

desktop/server app Desktop Desktop*

Main thesis

mobile app Desktop Mobile

http://bit.ly/PUI6Lk

Go cross-platform?JavaScript + HTML5

Platforms

iOS Objective-CAndroid JavaWP7 C#

http://bit.ly/PUI6Lk *approximatly; based on http://statcounter.com/ data

Native

+ fluently+ full OS integration

- difficult to reuse code

native vs. hybrid

Hybrid

+ easy code reuse + fast to develop+ immediate updates+ A/B testing

- doesn't deel native

http://bit.ly/PUI6Lk

Conceptual● different context● different hardware abilities

Conclusion

Technical● develop on desktop deploy to mobile● choose right technologies

http://bit.ly/PUI6Lk

Questions?

Artem SuschevSuschev.Artem@gmail.com