Wendong’s Smart Phone Weblog

Nokia just launched Nokia Forum Wiki.

Via AllAboutSymbian, we also have Sony Ericsson Developer Wiki and the Symbian Developer Wiki.

I did a 20-minutes google search and found out there are more out there:

Adobe Labs Flash Lite Wiki
Channel9 Windows Mobile Developers Wiki
HowardForums Wiki

And more from device manufacturers:
xda-developers wiki: HTC devices
Motorola Q Wiki

Wow. I am totally amazed by my findings

I read a very entertaining post from Adam Bien:
How to be Java Guru without knowing Java (at least in meetings)

I think you need to be a really Java guru to write that. I revised that list to “How to be Mobile Guru without knowing Mobile”. I am not a mobile guru and I do not have that good sense of humor. So some parts are just copy and paste. Any feedback is welcome

1. Before the initial project meeting go to jcp.org. Find all the JSRs under Java ME. Do not be intimidated by the total number (82). The most important ones are JSR 185 and JSR 248. During the meeting mention MSA subset, fully featured MSA, a few new JSRs and enjoy the impact.
2. If your project is going to be a realized with Java ME: emphasize the device fragmentation of Java. Depending on the nature of the project, point to other options like BREW (C/C++), Windows Mobile (.NET CF, C#), Symbian (C++/Open C), Flash Lite (ActionScript) etc.
3. Burn terms like GSM, CDMA, GPRS, HSDPA, HSUPA, UMTS, EDGE, 1xEV-DO, W-CDMA, WiMax … in your brain. Categorize them into 2G/2.5G/3G/4G technologies without hesitate.
4. Mention MIDP 3.0. (this strategy is very safe -> most manufacturers are now working on upgrading to MIDP 2.1 and MSA. Mention some features like MIDlet Concurrency.
5. Wait a random amount of time. Pick one of the vs. issues and try to initiate a dicussion; Java vs. Native, xHTML MP/Mobile AJAX vs. Java, Thin vs. Rich, Netbeans with Mobility Pack vs. Eclipse, AGUI vs. eSWT/eRCP etc.
6. Use terms like Mobile 2.0-ish, SOA-ish etc. Don’t care about the meaning: no one is able to define them.
7. Suggest more esoteric languages for mobile like Ruby, Python Basic and Pascal for prototyping, but not malbolge for the realization. In general there might be no reason to do that (Java is working well), but why not? Not many people realize that you can code Ruby on mobile.
8. Very important: mention things like team velocity, pair programming, ask about
   Xtreme-Programming, Agile, Scrum, Crystal, Test First, Mocking (the more the merrier).

Celltop from AllTel is based on Qualcomm BREW and uiOne technology.

MicroSoft ZenZui has touchscreen UI like iPhone. It looks similar to Nokia Widsets.

Acquired by Webwag, mobidget will be the first of its kind - widgets on demand available on both web and mobile. It is very promising.

Another mobile widget thing launched recently is Where GPS Widgets from uLocate.

Sony Ericsson launched its first Mobile Services Architecture (JSR 248) handset - Z750.

MSA umbrella standard JSR 248 includes:

* Security & Trust Services API (JSR177)
* Location API (JSR 179)
* SIP API for Java ME (JSR 180)
* Mobile 3D Graphics API (JSR 184) updated to version 1.1 from previous Java Platform versions
* Content Handler API (JSR 211)
* Scalable 2D Vector Graphics API for Java ME (JSR 226)
* Payment API (JSR 229)
* Mobile Internationalization API (JSR 238)

Sony Ericsson additions not mandated in MSA:

* Java Binding for the OpenGL® ES API (JSR239)
* Mobile Sensor API (JSR 256) for accelerometer applications

5ud0ku: a Sudoku game

just1: a Hitori game

Thanks to John M Flinchbaugh.