I discovered that Nokia and Samsung have some great java developer support for doing work on their phones.
Does anyone have any experience with them or others?
Regards,
Dr. A>
I discovered that Nokia and Samsung have some great java developer support for doing work on their phones.
Does anyone have any experience with them or others?
Regards,
Dr. A>
Most Sony Ericsson devices have on-device debugging - an incredibly useful feature from a dev. perspective.
Samsung & nearly all their phones are shite, I stay as far from them as possible.
Nokia can be both a blessing, and a curse.
Their devices tend to be consistent, and reliable, and their SDK is very well supported.
However their phones, while consistent, do tend to do things abit differently to others - often not following [and indeed often breaking] the midp spec.
Their SDK while being fully featured, and fairly accurate, is still pretty buggy - and can play havok with other SDKs.
Porting apps. that have been solely developed for Nokia’s can be a real bitch, as they tend to rely heavily on the Nokia extensions…
Out of the scores of phones i’ve worked with, i’d say my favourites are still the Sony Ericssons.
Ignoring the early T610 series (which is a pile of ****)
the newer Z1010, K500, K700, etc are all a joy to develop for - very accurately conform to the midp2 spec. and are all fast devices with on-device debugging.
Their own phone UI is also pretty sensibly layed out - so long as it hasn’t been vodafone-ised (aka made crap)
Have you worked with many Motorola phones? I can’t find any info on their SDK or any type of developer support the way I have for the other two plus SonyEricsson.
One thing I found about the SE phones was that they are EXPENSIVE. The first model that has MIDP2.0 support appears to be the P900. From there, things just get really tricked out and expensive.
Cheers,
Dr. A>
I’ve done a little work with Moto’s, mostly the C650 and moto triplet range. (V220,300,400,500,etc etc)
I’d rate them as pretty run-of-the-mill phones, average performance, fairly good implementations - I’ve had no need to go looking for the developer site.
Some of the SE phone are abit expensive, though the K500 is meant to be rectifying this.
Its basically a stripped down K700, no bluetooth, only 12mb ram instead of 30mb, slightly smaller resolution.
I think you can get it for around £100 on pay as you go, or for free on most contracts.
Its got it where it counts though, midp2, cldc1.1, JSR184(m3g), Mascot Capsule, 1.5mb heap, and its a pretty fast phone too. (infact, due to the smaller screensize, and newer firmware the K500 is a good deal quicker than the K700 :o)
(http://developer.sonyericsson.com/site/global/products/phones/phonegallery/p_phonegallery.jsp)
SE has good development documentation. Alot of info is available on their site and with their newer phones i’ve had exactly zero problems. Their forums are useless though, so if (when) you run into problems you are usually on your own.
Personally, I begun developing for them because of the On-Device Debugging but I feel that it has been kind of over hyped and isn’t nearly as useful as I first thought it would be.
ive made some good experience working with my motorola v525. and my (not too long) impression from their website
motocoder.com is very satisfiying. seems to be pretty frequented.