Slashdot Mirror
Best Platform For Hobbyist Mobile Development?
An anonymous reader notes a blog entry, possibly his own, comparing and evaluating 8 mobile platforms from the point of view of their suitability for a hobbyist programmer. Covered are iPhone, Java ME, Windows Mobile, Linux, Palm, Brew, Symbian, and Blackberry. The writer seems open-minded and is a strong fan of free software, but he gives the edge to Windows Mobile for this class of developer.
This piece reads more like a stream-of-consciousness than a carefully prepared technical article - maybe it's not meant to be considered as such. The author doesn't event attempt to justify a number of his assertions - in fact most of them seem to be based on some kind of vague "feeling" rather than concrete data or research.
Coming next to Slashdot: up is down and black is white.
We don't see the world as it is, we see it as we are.
-- Anais Nin
Not only is it not well written, many of the platforms are there just for show, as he knows nothing about them.
Examples:
iPhone
It's not clear he's developed for it. He spends his time whining about the closed SDK, which is valid enough, but could have simply said "Apple doesn't welcome outside developers currently". And left it off.
Blackberry
I can just quote him
"Next comes the blackberry, I have no idea about this as a programming platform so cannot say much about the SDK support."
Brew
And here:
Brew as a platform is great but its not a platform for a hobbyist programmer. The tools are "supposed to be good. I have never directly worked on a brew project so cannot say much about it."
Linux
(goes off boring us about his dislike of GPL (fine, but out of place). And then finally gets to the matter
(His JavaME and Windows Mobile coverage is decentish)
Of course, if it's just for yourself, you should check out the OpenMoko. It is the most open phone with the best developer support. You are literally writing GTK apps running on real Xorg and real Linux. And the whole point is that it's open, so no vendor trying to lock you out.
And the Neo 1973 GTA02 hardware is looking to be pretty sweet. Includes 3D accelerometer, GPS, WiFi, Bluetooth, and touch screen (with rumor of enabling multitouch through a driver update).
I don't have a lot of time, but I'll just quickly give you all my take, without going into details too much.
1. J2ME. It's the Java you all know and either love or hate, but with a different library. Some things work the same way as they do on the desktop. Some things work differently. And some don't work at all. Generally, there will be differences from device to device. Lots of devices come with J2ME implementations. Developing tools are freely available. J2ME seems to be a relatively stable target.
2. Linux. It's Linux. In theory, it's the same as desktop, server, etc. Linux. You should be able to use the same developing tools and libraries, which are freely available. In practice, devices may have odd differences and limitations compared to desktops running Linux. Sometimes, vendors go out of their way to introduce incompatibilities. It's a mine field. The number of devices Linux runs on is limited, and the ones you can reasonably limited are fewer still. Although the core of the platform is stable, parts of it are very much moving targets.
3. Windows Mobile (formerly known an Windows CE and Pocket PC). Pretends to be Windows but isn't. The platform has odd limitations and restrictions that differ from version to version and from device to device. Developer tools are available, but not necessarily free of charge. It all depends on the target device, its configuration, and the version of Windows Mobile. In general, you will have to pay for developer tools, compile different versions of your app for different targets, and pay for signatures on some targets. Many devices come with some incarnation of Windows Mobile on them. The whole platform is a moving target, with incompatibilities introduced at about every release.
The way I see it, of the three, Java wins hands down. It's the only one that is actually workable.
I don't know where Vivek is coming from when he says ``I never thought that Windows Mobile would take the pie, but for a hobbyist programmer they offer the best SDK's and you can make applications without worrying about certificates while testing and debugging. With a windows mobile one really feels in control, if you want to screw up your mobile device its really upto you. One rarely feels tied down the API's are clean and functional. Getting your first demo program onto the device takes a few seconds. It just makes sense to develop for windows mobile. There is almost no need to get your applications signed, at least for testing.''
To me, it has been the exact opposite of that. It's a nightmare. It's a nightmare to figure out what you have to download to get up and running. You can compile binaries for th platform with various tool chains, including some (user friendly for me) open source ones, but they won't run on all devices, as they will be lacking the right signatures. If you do get your application signed (which is costly; you have to sign every version of every exe, dll, and cab), it won't work on older releases that don't support code signing. The platform is almost ridiculously limited, and limitations aren't consistant across versions (e.g. you may or may not be able to get at a given file using the file open common dialog).
I'm thinking Vivek just tested things using one device, and was lucky enough that it didn't throw a tantrum.
Please correct me if I got my facts wrong.
This article contains less information than you'd get from 5 minutes of google searches on the names of the various technologies. Why reward such haphazardly written articles with frontpage coverage and ad impressions?
The author's few actual opinions about technologies are equally worthless; his rambling about Palm and J2ME makes it clear that he's never actually used the technology for more than a few minutes, and the ranting about Linux's license and the hassle of 'signing' applications makes you wonder if he's ever written any software at all. Someone who considers the Java Mobile API 'beyond him' probably shouldn't be writing articles about programming.
using namespace slashdot;
troll::post();
I used to work as a software consultant for a large company who shall remain nameless, making those in-car systems that integrate Navigation/cellphone/internet/car control all in one built-in unit in the car's dashboard.
They wanted to get away from their usual approach of having to make a whole new custom system for each car project, so we made a custom hardware platform running Windows-CE that we could sell to different car manufacturers just by modifying the front panel and changing some of the graphics.
Anyway I just told you all that to establish my experience and tell you that porting CE to a custom platform and developing drivers etc. for CE sucks very badly compared to doing the same with Linux due partly to the poor documentation and lack of support from Microsoft, and also that CE itself and its APIs are very badly designed and structured compared to Linux.
Sun is snatching defeat from the jaws of victory; give it another few years and they'll have thoroughly destroyed the mobile Java market as well, just like they did with the Java desktop market. You should try NetBeans 6, the developers have implemented great support for developing J2ME applications. There is even a GUI/Flow designer for Mobile devices included. It's true that before I had to spend a week configuring just to get Hello World up and running, but with a clean NetBeans 6 install I(and probably all of you) can do it within seconds. Also an emulator is included so you can test/debug on your computer, still if you want to test your application on your mobile device you just have to copy the compiled jar file over.
There are several samples included: like sounds, graphics, basic networking, games. I recommend everyone who is interested in developing application for mobile devices to check it out
But if you already hate Java, then just stick to the Windows platform. It's also very good.
Java EE is an utter mess, in my opinion. Too many acronyms and buzzwords and oh god the XML configuration files where everything has to be configured in three different places and then when you get something wrong it breaks and you can't figure out why... *deep breath*
That was my impression of it anyway. Some of it was incredibly useful, but all the unnecessary configuration just got in the way.
J2ME is nowhere near as complicated or difficult to get up and running. Eclipse, the EclipseME plugin and a compatible device are all you really need. The plugin does all the essential stuff for you, and having bluetooth on both the device and your PC makes deployment easy. For more serious stuff I use J2ME Polish (as in Mr Sheen), which handles handset compatibility and APIs quite well, as well as giving more control over the GUI.
That said, I got the distinct impression from TFA that, on the subject of J2ME, the author didn't have a clue what he was talking about:
For a start, MIDP 2.0 is part of the CLDC Wireless Toolkit. And as for "where am I supposed to test it"... well, the toolkit comes with an emulator for precisely that purpose. Most modern mobile phones are also MIDP 2.0 / CLDC 1.1 compatible, so that shouldn't be a problem. There are also optional APIs that the mobile manufacturers can provide according to the capabilities of the phone (for example, the Nokia N95 contains a GPS unit, so the Location API is included).
I'm not saying that it's the best mobile development platform out there, as I've come close to tearing my hair out when faced with some of it's limitations. But if there's one thing I can't fault it on, it's the shallow learning curve. I suspect the author wasn't really trying.
It is a shame that he doesn't bother to even mention anything about the BlackBerry platform. First and foremost, it *is* J2ME. (well, for the most part) You can run standard J2ME stuff on the BlackBerry, but you can also run stuff written against the BlackBerry-specific API. RIM provides free development tools, and while their own IDE is pretty poor, integrating their tools with the NetBeans IDE is pretty easy.
The biggest advantage of BlackBerry Java development, IMHO, is that the OS itself is practically a JVM, and the built-in apps are also Java. On most phones, running a J2ME app requires waiting forever for the thing to start and never integrate well. On the BlackBerry, your own Java apps start instantly and can look just like all the other built-in apps. Finally, BlackBerry is a common platform across a wide range of popular devices, so you'll always have plenty of potential users even if you build BlackBerry-specific apps.
And now for the shameless plug...
Back when I got my BlackBerry, I found that there were no decent available E-Mail clients for them. (only the service-based E-Mail, which stinks if you're not hooked to a corporate BIS server.) So, I kicked off an open-source project to write my own:
LogicMail - http://www.logicprobe.org/proj/logicmail