0
Phone for Me, Tablet for We:Building a multi screen appAbhay Aggarwal & Nitin Khattar
2Phones & Tablets –Are they different?
3Something happened…
4It’s all in the design
5One design, Multiple Personalities
6
7The Apple Bandwagon960 x 640 screen 1024 x 768 screen
8The Android Carnival1280x800800x4801024x600240x320240x400320x480360x640480x800540x960
• Highly fragmented mobile technology landscape• Need specialized resources or learn each technology• Production and maint...
10…Or, you can code smart
11Let’s build an app…
12The Key to Nirvana…
13#1IDENTIFY YOUR USER
14#2Sketch basic layouts for differentsizes
15#3CONSTANT = CONSISTENT
16#4Modularize your code
17#5Separate thebusiness logic from user interface
18#6Plan for data storage
19#7Use CSS & resource bundlesextensively
20Your thoughts
21</thanks>abhay aggarwal . aaggarwal@xebia.comnitin khattar . @khattarnwww.xebia.in
Upcoming SlideShare
Loading in...5
×

Phone for me, tablet for we mods

92

Published on

Published in: Technology, News & Politics
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
92
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
1
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • What is a phone? What is a tablet? Is it the set of feature? Is it the size? We could also look at Phone as a really tiny tablet, and at the tablet as a really large phone. In the right hands, and at the right time, either could mean the other.
  • How did we get to here? Innovation happened &amp; markets got disrupted. People, who might not necessarily be tech savvy, are consuming content on these devices, primarily because of the form factor. Strangely enough, or because of the design, children, as young as 2 years can actually use the new devices much better than most adults can do, because of one thing: The FINGER!!!!
  • The shape of the devices, aided in no small part by availaibilty of well written apps, is driving content consumption &amp; creation. The touchscreen practically begs the user to touch it &amp; play with it. Is it a coincidence that Facebook &amp; Twitter have expanded at precisely the same time that smartphones have been been made available? I think not.
  • The phone is a very personal device; an extension of one&apos;s own personality. The tablet, on the other hand, is a consumption/development/collaboration device, depending on the time &amp; place it is used.
  • Let&apos;s look at how the touchscreen device market looks like...
  • Right now, we have a plethora of devices. Things are still pretty simple in Apple&apos;s camp, where we have to worry about iPhone 4 &amp; iPad 2 dimensions.
  • Now lets look at Android. Its a huge mess, with differing form factors, and each manufacturer adding its own skin on top of the default Android UI. Now how does one code for all this? Do I make different apps for all markets?
  • Cross platform tools help you to code once, run many times.
  • .
  • The first &amp; foremost need is to understand the plethora of end users…..identifying the target audience &amp; enhancing the user experience/look &amp; feel based on that.
  • Point is to sketch the layouts in whatever medium possible. What one need is not a tool but a clear thought process and Understanding of varied sizes of multiple devices
  • What&apos;s the key here? Consistent UI, or Consistent Experience? (Hint: It&apos;s the latter) So what this means is that I might have to code extra, but I do not have to re-invent the wheel. If I can separate my business functionality from my UI, a lot of my work becomes easier
  • Try &amp; break your application into multiple modules….it helps in parallel development, reduces chances of failures &amp; bugs and lower external dependencies to a greater extent.
  • Code – Behind Pattern: always try separating entire business logic….whether domain objects, presentation models, services or utilities…from the user interface. In this way, it becomes easier for one to build apps for different platforms like mobile, tablets, web, desktop without rewriting the same code.
  • Each Device has its own hardware capabilities &amp; performance requirements. One should initially plan all the non-functional requirements like memory, speed, data storage separately for every targeted device.
  • Make extensive use of External and Runtime style sheets &amp; properties file to load any assets or themes. Handle Platform-Specific UI, DPI/Resolution Specific UI through CSS at runtime. Build easily different themes for different merchants/customers(might be of different age groups)
  • Transcript of "Phone for me, tablet for we mods"

    1. 1. Phone for Me, Tablet for We:Building a multi screen appAbhay Aggarwal & Nitin Khattar
    2. 2. 2Phones & Tablets –Are they different?
    3. 3. 3Something happened…
    4. 4. 4It’s all in the design
    5. 5. 5One design, Multiple Personalities
    6. 6. 6
    7. 7. 7The Apple Bandwagon960 x 640 screen 1024 x 768 screen
    8. 8. 8The Android Carnival1280x800800x4801024x600240x320240x400320x480360x640480x800540x960
    9. 9. • Highly fragmented mobile technology landscape• Need specialized resources or learn each technology• Production and maintenance costs overshoots the budget9Become a Native App Developer…
    10. 10. 10…Or, you can code smart
    11. 11. 11Let’s build an app…
    12. 12. 12The Key to Nirvana…
    13. 13. 13#1IDENTIFY YOUR USER
    14. 14. 14#2Sketch basic layouts for differentsizes
    15. 15. 15#3CONSTANT = CONSISTENT
    16. 16. 16#4Modularize your code
    17. 17. 17#5Separate thebusiness logic from user interface
    18. 18. 18#6Plan for data storage
    19. 19. 19#7Use CSS & resource bundlesextensively
    20. 20. 20Your thoughts
    21. 21. 21</thanks>abhay aggarwal . aaggarwal@xebia.comnitin khattar . @khattarnwww.xebia.in
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×