Fitting content to domain

3,301 views
3,273 views

Published on

I made this ppt to educate my sales team about various domains and the kind of applications which would work on each domain.

Published in: Business, Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
3,301
On SlideShare
0
From Embeds
0
Number of Embeds
171
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Fitting content to domain

  1. 1. Matching domains & content Matching a domain to the content which a client has to offer is not an easy thing…but for the success of an application, it is everything !
  2. 2. How do you match a domain? … fit a lifestyle … fit a pocket … fit a use
  3. 3. Perfect match! <ul><li> Masses – When you have a service that can be used by anyone and every one, SMS is the most apt platform for it </li></ul><ul><li> Lyte bytes – Works only for information which can be served broken down into bits and bytes & fit into 140 characters! </li></ul><ul><li> Clear revenue model – When the service seeks to earn in today’s scenario. (This may not be the same 6 months into the future) </li></ul><ul><li> Great take-off point – the SMS platform is a great take-off point for any company to step into the world of mobility </li></ul><ul><li> Forget-able – The world of keywords and short-codes is fast becoming a swamp where the user gets lost very often… </li></ul>SMS
  4. 4. Since it is difficult to remember keywords and short codes SMSs work best instantly. For instance TV polling where the number and keyword is announced, immediately after a broadcast where instructions and short code are sent etc
  5. 5. Perfect match! <ul><li>All devices – A basic WAP site works on all WAP enabled devices…nearly 90% of all devices hitting the market at the moment are WAP enabled </li></ul><ul><li> No control – On a WAP application, it is not possible to control anything on the device…unless a page refreshes, which is intrusive for the user. </li></ul><ul><li> Works well for dynamic content- Where content is controlled by dynamic entities on a server.. i.e. membership based services, browse-able databases etc. </li></ul><ul><li> No Processing can be done – All processing of WAP content happens on a server… no processing like calculations, validations etc can happen on the device </li></ul><ul><li> Graphically light – Any WAP application, be it in WML or XHTML has to be graphically light because neither band-widths nor screen sizes and resolutions are appropriate for heavy graphic use </li></ul><ul><li> Personalization possible – Since mostly we build for MSISDN forwarding networks, a high degree of personalization is possible in a WAP application </li></ul>WAP
  6. 6. WML Basic XHTML layout
  7. 7. When a client wants both reach and branding. We can offer both XHTML & WML at an extra cost. They can be served appropriately to appropriate devices!
  8. 8. Perfect match! <ul><li>Highly interactive – Java applications can work functions which require processing on the device itself. E.g. calculations, validations, interaction with phone features like calling, picking up a calendar etc. </li></ul><ul><li> For dynamic interactions, GPRS required – although simple query sending applications work on SMS alone, for any interaction where information is required from the server, GPRS works best </li></ul><ul><li> Possible to do event based alerts - Information can be queried from the server in the background without disturbing the interface. Works well for event based apps . E.g. cricket scores </li></ul><ul><li> Device issues – applications don’t work consistently on all devices. Each type of device requires customization </li></ul><ul><li> Excellent branding opportunity – Once the application is downloaded by a user, the application icon with the company’s branding denotes a presence in the user’s personal space </li></ul>J2ME Basic
  9. 9. Perfect match! <ul><li>High functionality – Any function which is possible on a phone can be done on an advanced Java app. Click a photo, upload photo, Get profile, edit profile…etc. </li></ul><ul><li>Location processes – it is possible to process the exact location of the user instantly using the latitude and longitude positioning system </li></ul><ul><li>Bells & whistles – Advanced J2ME apps can have everything from sounds, to animations like screen transitions etc. </li></ul><ul><li> Device issues – for the java application to work for the entire target audience – extensive testing as well as development is required </li></ul><ul><li>Secure transactions – 128 bit encryption is possible on advanced J2ME applications. </li></ul>J2ME Advanced
  10. 10. J2ME Basic J2ME advanced
  11. 11. Applications where a medium level of interaction with the phone features is required i.e. pick-up a contact from the address book, upload a file from gallery, get calendar etc. can be made in J2ME
  12. 12. Applications where security is a priority should be made in J2ME. The values stored in a J2ME app can not be retrieved unless by the application is designed to do so. 128 bit encryption is possible!
  13. 13. Perfect match! <ul><li>A class apart – applications which are meant for educated phone enthusiasts. The high income gang who don’t have time but have the phone and can use it to save time and effort. </li></ul><ul><li> Only works on medium to high end phones – Will only work on Symbian phones. Which mean medium end phones. Mostly Nokia – although a few high end phones of other brands are also sport the Symbian OS. </li></ul><ul><li> Possible to change phone behavior - You can add extra menu commands, show icons, have text scroll across the page, have alarms ring, have alerts pop-up. Almost anything is possible with a Symbian application </li></ul><ul><li>Easy to use applications – Symbian applications are easy to use because a lot of the interaction patterns in a Symbian app are the same as interaction patterns on the phone. It even looks like the native phone GUI! </li></ul><ul><li> Developmental effort – There is huge developmental and testing effort needed for Symbian applications </li></ul>Symbian
  14. 14. Sample Symbian app – Yahoo Go! Notice how this uses the same UI pattern as the phone pattern Yahoo Go uses the same contact list as the phone native list Yahoo e-mails come in the same messaging system used for text messages Yahoo To-do list is imported to the phone To do list and is synced with the internet through GPRS Yahoo photo album can be used through the same system as the phone’s photo gallery
  15. 15. When you require the application to enmesh with the phone to the point where the user does not know whether a feature is there because it is a phone feature or an application feature, you use Symbian!
  16. 16. Perfect match! <ul><li>Gorgeous applications – With flash you can make graphics intensive applications with all kinds of bells and whistles. Swipes, images, animations etc. </li></ul><ul><li> Only works on Flash enabled phones – The market statistics on how many truly flash lite enabled phones are being used by Indians out there are pretty cloudy </li></ul><ul><li> Very apt for web to phone applications - web to phone applications turn out exactly as planned if you get the screen size correct! </li></ul><ul><li>Consistency – There is consistency on the behavior of flash lite apps on Flash lite enabled phones! </li></ul><ul><li>Freedom – You can make downloadable applications or applications which run on phone browsers for any purpose! </li></ul><ul><li> Very limited phone interaction – These applications are not suitable for interactions where phone features like calling, accessing contacts, photos etc. are required! </li></ul>Flash lite
  17. 17. A flash lite application can be made for a very very niche audience. E.g. users of N93, E 24, P990 etc. Design effort is considerable but doable!
  18. 18. Thank you

×