I've been poking my nose in mobile software development since 2000, starting on what was then the ER5 and Ericsson's R380. Since then I've been doing a bit of everything on the S60 Platform, from learning its bits and pieces to helping others find their way trough the maze.
ltomuta | 08 December, 2008 09:00
"Note that Android Dev Phone 1 devices are not intended for non-developer end users. Since the devices can be configured with system software not provided by or supported by Google or any other company, end users operate these devices at their own risk."
CommentsJOM | 08/12/2008, 11:44
If that developer phone is the ONLY way to get G1 (e.g. in Finland), then price comparison to T-Mobile doesn't make much sense. One offer, one price, take it or leave it :)
Have to admit that it does seem risky to allow such customizable phones into public phone networks. Could they bring down networks, will we see law suits against Google because of those?
Cheers,
--jouni not going to get G1, but following the situation with interest
ltomuta | 08/12/2008, 13:29
True, yet you will still need some kind of contract (whatever the option) on the developer device so that adds up to the cost of the phone too.
But I think the price diference is still signigicant enough to keep the end-users away. And that's the point.
It goes a bit to a previous exchange about "pay to develop" which it is not a bad thing necessarely, even from an "open source" perspective.
tote_b5 | 08/12/2008, 23:38
It's a big headache to find the right carrier and make a contract with them to sell your phones. It limits the spread of your devices, too. So why not offer the same device for *everyone*?
Of course, it can't be offered at the same price as what Google's customers (i.e. the carriers) are selling the phones with a binding a contract (although for Google it would be the same), because then who on Earth would buy the phones from the carriers?
Can it pose a risk to operators' network? Well, if they demand a certain level of maturity and reliability from *official* Android devices (i.e. those that are shipped by Google to the carriers) to be kept and which can now be changed by anyone (software-wise), then it naturally poses a risk imho. But I'm also sure that Google has already negotiated with operators first before making this step.
Sorcery-ltd | 09/12/2008, 11:26
The developer phone doesn't also need a contract. I (presumably like most mobile software developers) have a drawer full of phones but certainly not a contract (not even a SIM) for all of them.
However, I agree that it would put ordinary customers off from buying them, since they would presumably need a contract too (although in the UK at least you can get significantly better deals on SIM-only contracts).
As for threat to the network, I've been using phones with "experimental" firmware for many years - it's really difficult to do any damage to the network by accident. Of course malicious attacks are another issue but there are already plenty of relatively low cost options for someone wanting to do that which require much less effort that understanding how to program device firmware.
Mark
That's $180 + contract
Sorcery-ltd | 08/12/2008, 11:28
I don't think the devices are significantly more expensive for developers if you factor in the cost of a T-Mobile contract on top (not required for a developer with an unlocked phone).
However, "hardware unlocked" is interesting and potentially worth paying for. I don't think there's much additional risk for the networks on a dual-chip phone above allowing open platforms in general. If developers could re-flash the cellular modem software that would be another story.
Mark