Twitlet Interface Design Decisions
When designing Twitlet, a Java ME (J2ME) Twitter interface, we made some conscious GUI design decisions in order to overcome fragmentation issues. On this project we wanted to have a single JAR file for all devices.
(1) No soft key menus. We didn't want to use the native soft key menus because they look ugly and if we chose to use custom soft key menus we would have had to worry about mapping the menu options to the actual keyboard soft keys which is a difficult and time consuming undertaking.
(2) Native text input screens. We didn't use custom text input boxes because, once again, we didn't want to worry about keyboard mapping across different devices. Another reason is we wanted access to T9 capabilities which isn't possible in custom text input areas.
You can download the application by pointing your mobile browser at mobile.paxmodept.com.
(1) No soft key menus. We didn't want to use the native soft key menus because they look ugly and if we chose to use custom soft key menus we would have had to worry about mapping the menu options to the actual keyboard soft keys which is a difficult and time consuming undertaking.
(2) Native text input screens. We didn't use custom text input boxes because, once again, we didn't want to worry about keyboard mapping across different devices. Another reason is we wanted access to T9 capabilities which isn't possible in custom text input areas.
You can download the application by pointing your mobile browser at mobile.paxmodept.com.
~Add Comment~

