Going mobile with Kentico CMS


Published on

As mobile internet usage increases in popularity, we have to be more aware of how to adapt to this technology. Webpages made using Kentico CMS are capable of being used on mobile devices. We will show you how to prepare your websites for them. Attend the Kentico Connection 2010 conference to learn more.
All over the world, the market share of smartphones and 3G phones is rapidly growing. Thanks to companies like Apple and Blackberry, internet usage through mobile technology is becoming a habit not only for businesspeople, but everyday phone users as well.
More than ever, preparation of websites for mobile devices is needed for websites to satisfy their viewers.
In this session, we will focus on main differences between traditional websites and websites for mobile devices.

Since Kentico CMS supports mobile devices, we will present:
How to make your websites ready for mobile phone viewing; and
How to share content between your main website, your website’s mobile counterpart, and more.

Published in: Technology, Business
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Data source - http://searchengineland.com/top-10-reasons-your-website-should-go-mobile-32566 http://www.bizreport.com/2010/02/time_spent_with_mobile_internet_increases.html#
  • Source: http://www.articlesbase.com/international-marketing-articles/top-ten-bestselling-cell-phone-in-april-2010-2264987.html
  • Going mobile with Kentico CMS

    1. 1. Going Mobile<br />Thom Robbins<br />Thomasr@kentico.com<br />Twitter: @trobbins<br />
    2. 2. Agenda<br />The mobile marketplace<br />A mobile attack plan<br />It’s all about the content<br />Mobile best practices<br />
    3. 3. Mobile opportunity – Data and Hype <br />Expected 9% growth in 2010<br />Estimated 2 Billion cell phones worldwide (hand me downs included)<br />93% of US adults own a cell phone (ubiquitous technology)<br />YouTube accounts for 36% of total video traffic on mobile networks worldwide<br />1.6 Billion purchased from mobile devices in 2009 (increasing buyer confidence)<br />7.5% of the top 500 online retailers have a mobile website/iPhone app<br />Mobile advertising spending will surpass 6.5 billion in 2012<br />Users average 13 hours online total per week, up from 7 hours in 2002 (Ruder Finn report – Americans spend 3 hours using the mobile web)<br />“Desktops will be irrelevant in 3 years time”<br />John Herlihy – Google<br />
    4. 4. What are people doing?<br />Mobile users are opportunistic!<br />91% of mobile consumers use the Internet to socialize (compared to 79% of desktop users)<br />45% engage with social networks<br />62% use mobile for instant messaging<br />40% read content<br />Mobile users watch videos (dominate traffic form)<br />Mobile users are more likely to research subjects<br />Men are more likely to use mobile as an ‘escape’ (Not me of course!)<br />
    5. 5. Top selling phones in 2010<br />Reflects more than 50 countries across six continents mobile phone sales (not all inclusive list!) –<br />1. (2) Nokia 3720 Classic <br />2. (1) Apple iPhone3G<br />3. (3)  HTC HD2<br />4. (-)HTC Desire<br />5. (-)Sony Ericsson XPERIA X10<br />6. (-)Nokia 2730 Classic<br />7. (10) Samsung B2100<br />8. (-)Sony Ericsson Vivaz<br />9. (5) Nokia E52<br />10. (-)HTC Legend<br />Note: () = last month rankings<br />
    6. 6. Pulling it together<br />The Device<br /><ul><li>Web browsers
    7. 7. Constrained browsers
    8. 8. Proxy browsers
    9. 9. Limited controls
    10. 10. Limited screen size
    11. 11. Limited memory and bandwidth
    12. 12. Limited typography
    13. 13. Limited color palette</li></ul>The Environment<br /><ul><li>Variable accoustics
    14. 14. Variable lighting
    15. 15. Variable mobile coverage</li></ul>The Audience<br /><ul><li>Looking for answers (SEO is important)
    16. 16. Looking for local answers
    17. 17. Looking for local answers now
    18. 18. Ready to pay for local answers now</li></li></ul><li>A pause for marketers<br />Three things to consider when developing your mobile strategy<br />Are you building only a lead generation strategy? Mobile strategies shouldn’t always be about lead generation. The form factor makes it extremely hard to perform extensive lead generation for marketing. The mobile platform does serve well for furthering existing customer relationships<br />Have you clearly defined your objectives? Like any marketing and development strategy what are your key objectives? What is your audience demographics? These are important parts of developing an effective mobile strategy.<br />Have you defined accurate measures? Like any marketing strategy defining accurate measures is extremely important. Unlike other marketing strategies small devices have limited capabilities and you always need to be careful with increasing bandwidth.<br />
    19. 19. A mobile attack plan<br />Provide a mobile alternative<br />Build a device specific application<br />
    20. 20. Provide a Mobile Alternative<br />Guiding principles:<br /><ul><li> Alternate design and layout
    21. 21. Tactic: Kentico redirection web part
    22. 22. Tactic: Kentico CMS API
    23. 23. Tactic: .NET API
    24. 24. Simplify user input
    25. 25. Tactic: Simpler design
    26. 26. Reduced requests
    27. 27. Tactic: Windows Communication Foundation (WCF)
    28. 28. Adaptive design
    29. 29. Design adapts to mobile environment
    30. 30. Battery warnings
    31. 31. Lost connection
    32. 32. Linked phone calls (it is a phone!)
    33. 33. Graceful degradation
    34. 34. Notify user when personal info is selected
    35. 35. If denied a request degrade slowly
    36. 36. No clutter CSS
    37. 37. Flow based layouts</li></li></ul><li>Check out the Mobile sample site<br />Site home page contains redirection to /Mobile<br />Dedicated CSS stylesheet (Corporate Site – Mobile)<br />/Mobile node<br />Works as a master page for the mobile section<br />No template inheritance from main site <br />Sections available<br />Home – redirected page with a Repeater dynamically loading content from the Editable region on the main Home page<br />News – Repeater displaying news with a transformation<br />Articles – Dedicated mobile section and content is not shared<br />About us – Two editable text web parts only in Mobile section<br />
    38. 38. How does it work?<br />Captures HTTP request<br />
    39. 39. Extending redirection – device targeting<br />CMS.GlobalHelper<br />Browser must report as mobile<br />Best Practice Tip<br />Exploit the ASP.NET Request object (Request.UserAgent)<br />Check for iPhone<br />iPhone User Agent<br />Mozilla/5.0 (iPhone; U; CPU iPhone OS 3_2 like Mac OS X; en-us)AppleWebKit/531.21.10 (KHTML, like Gecko) Version/4.0.4 Mobile/7B334b Safari/531.21.10<br />Check for Andriod<br />Check for iPad<br />
    40. 40. 5 minute mobile makeover - CSS patterns <br />Common design pattern (Eliminate clutter)<br />single-column, fluid width, three main sections: header, main content and footer<br />Best Practice Tip<br />Tab-based navigation, tabbed links with relative width and horizontal menu<br />Modify Stylesheet<br />Don’t forget smaller form factors!<br />
    41. 41. Build a Device Specific Applications<br />Tap into native application integration<br />Caters to occasionally connected devices<br />Caters to device features<br />Marketplaces (fame, fortune and exposure)<br />Tools: Appcelerator Titanium<br />Tools: MobiOne<br />Tools: Visual Studio<br />
    42. 42. Mobile<br />PC<br />Mobile<br />iPad<br />API Layer<br />Kentico CMS<br />WW Data<br />It’s all about the content!AKA: I see data!<br />
    43. 43. Exposing content (Approach 1) REST<br />What is REST?<br />REST stands for Representation State Transfer<br />Conceived in 2000 as a doctoral dissertation by Roy Fielding (a principal author of HTTP protocol)<br />REST is about accessing resources through a universal interface (web browser)<br />RESTful URLs are addressable http://www.mysite.com/Products/Item300<br />Why REST?<br />Leverages scalability of the Web<br />Site scalability through caching and session state<br />Easier URLs<br /> Simplifies SEO<br /> Consistency with the design of the World Wide Web<br /> Can leverage generic client components (ex. jQuery controls) and dev skills<br />Why not REST?<br />If you need advanced collaboration between applications like distributed transactions (WS-*)<br />If you need to use a protocol other than HTTP<br />REST is an architectural style, not a specification!<br />
    44. 44. Bit.ly Restful Example - simple<br />protected void bGetInfo_Click(object sender, EventArgs e)<br /> {<br /> string apiKey = "&apiKey=APIkey";<br /> string loginKey="&login=rusername";<br /> //encode the string<br /> string shortUrl =shorturl"&shortUrl= "+ Server.HtmlEncode(txtURL.Text);<br /> // Format for string sent is - http://api.bit.ly/v3/clicks?&shortUrl=http%3A%2F%2Fbit.ly%2FavNcS4&login=login&apiKey=key&format=xml<br /> // URL must be encoded<br />WebRequestreq = WebRequest.Create("http://api.bit.ly/v3/clicks?" + shortUrl + apiKey + loginKey);<br />WebResponseresp = req.GetResponse();<br /> Stream stream =resp.GetResponseStream();<br />StreamReadersr = new StreamReader(stream);<br /> String s=sr.ReadToEnd();<br />txtInfo.Text=s;<br /> }<br />WebRequest<br />WebResponse<br />
    45. 45. Unifying all the options (Approach 2) - WCF<br />Up front work is required!<br />Wow! Look at all the options in WCF!<br />
    46. 46. WCF – Unified programming model<br />.NET Remoting<br />ASMX & WSE<br />Interop<br />with other<br />Platforms & WS-*<br />Extensibility<br />Location transparency<br />Attribute- <br />Based<br />Programming<br />Message-<br />Oriented<br />Programming<br />REST / HTTP Programming<br />Enterprise Services<br />System.Messaging<br />HTTP Services<br />
    47. 47. WCF ABC (Address, Binding, Contract)<br />Endpoint<br />A<br />B<br />C<br />A<br />B<br />C<br />A<br />B<br />C<br />Client<br />Service<br />Endpoints<br />Message<br />Address<br />Binding<br />Contract<br />(Where)<br />(How)<br />(What)<br />
    48. 48. webHttpBinding<br />New “web-friendly” WCF Binding in Fx 3.5<br />Allows for the development of RESTful services<br />Does not use SOAP envelopes<br />HTTP and HTTPS Transports Only<br />Supports several wire formats:<br />XML<br />JSON<br />Binary (streams)<br />
    49. 49. WebServiceHost<br />Specialized SerivceHost for RESTful services<br />Eliminates need for lots of configuration<br />Automatically configures address, binding, contract<br />Optimized for single-endpoint services<br />Use from .svc file:<br /><%@ ServiceHost Language="C#" Debug="true" <br /> Service="Caching1.FeedService" Factory=“System.ServiceModel.Activation.WebServiceHostFactory” %>"%><br />
    50. 50. [WebGet] And [WebInvoke]<br />Binds a WCF operation to URI space and HTTP method<br />Indicate the HTTP Method for the operation<br />WebGet – Don’t make me write it<br />WebInvoke – All verbs other than GET (Method parameter takes in the name of the Verb)<br />Other Parameters<br />BodyStyle – Indicates whether the Request/ Response are wrapped or not<br />RequestFormat – Json or Xml<br />ResponseFormat – Json or Xml<br />UriTemplate – Rich binding to URI<br />
    51. 51. UriTemplate<br />String that allows you to define the structure of the URI, as well as to define “Holes” <br />The “Holes” are variables<br />You Bind the template with parameters to fill the holes<br />{productId} hole / variable gets bound to productId parameter in operation<br />[OperationContract]<br />[WebGet(UriTemplate=“product/{productId}")]<br />Product GetProduct(intproductId);<br />Variable<br />
    52. 52. Mobile site best practices<br />Organize navigation logically for mobile users<br />Put navigation buttons below content to avoid scrolling<br />Place popular buttons first<br />Make word links shorter for space<br />Use optimized heading tags<br />Keep information three clicks from home page<br />Degrade application gracefully<br />Allow social bookmarking and tagging functionality<br />Avoid pop ups<br />Submit a separate site map to Google<br />Run a mobile site back link campaign <br />
    53. 53. Things to avoid..<br />Flash (Depending on device)<br />Frames<br />Cookies (many newer devices will support)<br />User tables sparingly<br />Nested tables<br />Absolute measures (100px wide can be half the screen)<br />Using a lot of fonts<br />
    54. 54. Tips for images<br />Images must be small<br />Saving a 3 color file into a 256 color indexed GIF increases size<br />Photoshop has a nice option to reduce this (Image mode – indexed and then choose web colors)<br />Images must download quickly<br />Beware of clutter factor<br />Don’t put large images at the top of the page<br />It’s annoying to have to wait<br />Exception: Photo gallery<br />
    55. 55. Additional Information <br />Did you get your poster? <br />Best samples are in your project!<br />Don’t forget to attend the API session tomorrow<br />Documentation - http://devnet.kentico.com/Documentation.aspx<br />Code Snippet Library - http://devnet.kentico.com/Blogs/Thomas-Robbins.aspx<br />Marketplace - http://devnet.kentico.com/Marketplace.aspx<br />