4 ms·
Oh come on. It's easy to piss on stuff that could be better, but Android is actually a fine platform to develop for, and plenty of applications are showing up.
by davidw 17y ago
Oh come on. It's easy to piss on stuff that could be better, but Android is actually a fine platform to develop for, and plenty of applications are showing up. Sure, not as many as iPhone, yet, but there are some pretty cool ones out there.
And it's not "the only hope" - there will be more Android phones out, and the whole thing will only continue to improve.
- blasdel 17y agoThere are some huge holes in the Android APIs that make writing well-produced games extremely challenging. The Audio APIs are particularly shitty, making it basically impossible to have worthwhile soundfx. I just looked and it's now finally possible to read incoming Audio without waiting for the user to finish recording! (though they still don't call it streaming) That you're stuck in their unjustifiably-oddball bytecode-interpreter sandbox (no JIT!) makes it particularly hard to just implement things yourself in 'userspace'. People have been saying "there will be a glut of Android phones out in a few months" for well over a year. This is the first Android hardware that isn't obviously a pile of shit -- it's actually better than the iPhone in many ways! Now we get to see if the software can live up to it.
- davidw 17y ago> That you're stuck in their unjustifiably-oddball bytecode-interpreter sandbox (no JIT!) It's pretty evident if you think about it: they wanted something open source under a liberal license (Apache/BSD rather than GPL), and so did not want to touch Sun's Java implementation. Therefore, they did their own thing, which is a much solution than hassling with Sun about licensing. I suspect we'll see performance improvements with time; it's not as if Google doesn't have the resources to create a JIT if/when they want.
- nwatson 17y agoFor low-level performance-critical stuff you can always go down to C++, though I believe that's limited to operations on your own internal data and does not extend to system-level programming.
- unalone 17y agoFake Steve Jobs illustrated the biggest Android problem: When your operating system is designed to be modified for each individual phone, and each phone runs a modified version of the system, then you can't reliably develop for it in the way you can for the iPhone. If I make an iPhone app, then it'll work for every person with an iPhone and every person with an iPod touch. The same's not true for Android, which is why developers are reporting failures with the applications they're designing for it. I've never used Android, unfortunately—can't find people with the phone to irritate/mug—but I'd imagine it's good, and I like that Google's released an OS with some focus on being good, because cell phone companies showed in the last decade that they don't give a damn about good when left to their own devices. Where I don't have faith in it, though, is in its attempt to make a developer haven that the iPhone doesn't offer. It seems that there're integral problems to its developer experience that won't fix themselves easily.
- davidw 17y agoIt's a problem, but I don't think it's an impossible one, and nor do I think the answer is that everyone everywhere should have the exact same phone. The Android guys, who are not stupid, certainly have J2ME to look at as an example of what could go wrong. And, to tell the truth, even J2ME is certainly painful once you try and taret a wide number of devices, but not impossible.
- codedivine 17y agoOn the other hand, it shouldn't be too hard really. People have been developing desktop apps for myriad resolutions for years.
- unalone 17y agoYes, but we're talking very small screens here, with very little room for design. When you can design any application to run at 800x600, then maybe you don't fill every screen but you have enough space to do what you want. When you're dealing with very small screens, some of which are multitouch and some of which aren't, some of which have physical keyboards and some of which don't, then you have to juggle a lot of variables and the quality of your design suffers. I shouldn't have to point out the level of build in the iPhone apps gallery. Those applications are gorgeous. Better than most PC apps, I'd argue, in their compactness and elegance. Developers have an edge on the iPhone because there's an established design standard, and there's an established screen size. So they can spend as long as they need fiddling to make their app perfect within those confines. On Android, that's not possible. To use an unnecessary metaphor, iPhone apps are haiku and Android apps are open verse. On the one hand, it's nice not to have limits, but on the other, you find it's much easier to make something beautiful when you're given set restraints with which to riff on.