Friday, 15 January 2010

Content Management System targeting Mobile Devices -


If I want to implement CMS for mobile devices, then what kind of points should be kept in mind? For example, to reduce page size, use customized (smaller) pictures any other ideas?

Also, what types of rules can be implemented when changing web pages designed for desktop browsers, as well as web browsers that are easily displayed in mobile browsers?

I know that the mobile device is widely varying in capacity and property, but still trying to list some rules.

Apart from this, any other suggestions, suggestions, questions and advice are welcome on this subject.

Thank you for your opinions and answers.

Short introduction, I have all the things listed below


Phone Identifying

While working as a web context with mobile, it is absolutely mandatory that you correctly identify the phone. This should be a top priority; Here are some problems with recognizing the phone and their features:

  • userAgent.contains ("iPhone") Do not use. is already loaded in web bots and other applications wherein iphone is included in its user agent string and thus you recognize them incorrectly.
  • Do not send user-agent to all phones headers Although some of them send URLs: s, in which the format features all the phones. Unfortunately this presents the next two problems:
  • Obviously you will not have access to any device data there and you are bound to use the public data treasure such as . These databases, however, are incomplete, have to stay a little back or do not have the data you want, although these are your best bet for the initial data set.
  • UAProfs lie. Yes, there is false information in it - lots of it! This is partly because the creators forget to update XML and partially because UAProf files are written during the development of the phone and as we know, the features change during development.
  • On a feature when dependent, make sure that you are not relying on the specific version of a particular phone. For example BlackBerry has a feature named Tile which is actually a great bookmark but you only have it all BlackBerry phone, to identify the operating system version of the actual phone to meet the correct variation of the tile For the touchscreen, the same iPhone was not the first with the touch screen and most certainly not the only one - it is not even expected of such a situation where Only one type of processing is input, for example, touch screen, physical keyboard and stylus too.

Creating Original Page

Thankfully that some such people have agreed and when you make pages, you should use it. But oh how things will be so easy ...

  • All phones have different levels of XHTML-MP / CSS support. For example, if I remember correctly, do not support background color for some older blackberry block elements or whenever header tags are many, we also have span has seen the wrong sequence of elements oh and for some reasons tables are really hard. In fact, you have to go lower on markup / styling invoices.
  • You can not test the existence of the feature using the feature. If you want to detect JavaScript support, you might think that by adding some JavaScript to the page will work for that purpose, right? No, it crashes a significant percentage of mobile phones coming to your site. Of course, new phones are not crashed but everyone has bought their phones in the last 12 months apart from the mobile specific javascript API: according to each manufacturer is different, because at present the low to detect JavaScript-based geographic location There are three separate APIs: None of them are interoperative with others.

Add all of these to the top of the usual CMS features (security, content management and changes, caching, modularity, visitor tracking and whatnot) The picture should be how everything affects everything and how you really should consider the cost of making yourself.

In fact though it is against the general sense of SO SO, I strongly suggest that you get the solutions that are easily prepared like our and instead your site Use it for the need to build. Eventually, our product has a special development of seven years under its hood.


No comments:

Post a Comment