I'd go for option 2 as the priority. The CSS solution sounds good, but with all the javascript in the page I think you might find that it just doesn't work on the vast number of mid-range handsets. Pages may not be rendered at all and in the worst case the browser and phone will crash. It's scarily easy to crash some handsets with markup. There is a good mobile Twitter service called dabr (http://www.dabr.co.uk) that just happens to be an open source project written in PHP ( http://code.google.com/p/dabr). It uses the Twitter API to access the raw functionality. I've just started modifying the code to get it to talk to laconica. So far things look promising and it could form a good basis for the laconica mobile interface. While it doesn't get 100% clean bill of health with mobileOK checker or ready.mobi the problems are very minor.
Martin I'd like to propose a mini-roadmap for laconica mobile user experience: > 1. Create screen and handheld media stylesheets that is geared toward small > viewing area. This means that some of the content (e.g., text, images), will > be invisible or repositioned. Good: adapted UI; less good: page weight > remains the same. I think we can get this rolling incrementally; cover major > mobile browsers (laconica 0.7.x and 0.8.x). > 2. Create a mobile space e.g., http://m.identi.ca that contains > a reorganized version of the content and have its own screen and > handheld media stylesheets. Good: Lightweight and on the go UI and less > good: we don't (yet) know what the heck users want =) I think it needs > more careful planning, so, we can perhaps have it for laconica 0.9.x or 1.0. > 3. WML ~ I'm not sure if we really need to take this on too. Perhaps we can > revisit this during or after #2. What do you think? > -Sarven
_______________________________________________ Laconica-dev mailing list [email protected] http://mail.laconi.ca/mailman/listinfo/laconica-dev
