4 ms·
Um, I'll try: So it's really the same as a "computer-computer", but with a specific UI framework and peripherals like a compass, GPS, camera (as you mentioned)
by allo37 6y ago
Um, I'll try:
So it's really the same as a "computer-computer", but with a specific UI framework and peripherals like a compass, GPS, camera (as you mentioned), etc.
Where it starts to suck is the interface for interacting with all those things: So you want to access your device's location? Well do you want to use the cellular/WiFi network, GPS, or both to tell you where you are? Ok, you figured that out, now how fast do you want updates? Oh, that was more of a suggestion - what's the fastest we can send you updates? And so on.
And it's like that for almost EVERY. SINGLE. THING. Imagine someone sat down to develop a mobile API, then got bored halfway through and decided to just leave the rest as an exercise to the user. And then some other people decided to come along later and add "improvements" (i.e: what Apple is doing) to the mishmash of existing "stuff", and you basically get Android development.
Yes, iOS is better, at least in my opinion. It's hard to pin down, but you get the sense that at least they designed it for someone who actually wants to write an app.
- detaro 6y ago> Where it starts to suck is the interface for interacting with all those things: So you want to access your device's location? Well do you want to use the cellular/WiFi network, GPS, or both to tell you where you are? Ok, you figured that out, now how fast do you want updates? Oh, that was more of a suggestion - what's the fastest we can send you updates? And so on. Given its a mobile device with battery limitations, those seem to be reasonable inputs to want for an API?
- allo37 6y agoMy issue is more the amount of "knobs" you're presented with that seem to have overlapping responsibility. It's very difficult to figure out which ones are "right" (idiomatic?) so it makes for a very confusing implementation. Compared with iOS which gives you many of the same controls but at least presents them in a clear, unified way.
- ryan-duve 6y agoAh, I think I understand now. It's more of a death-by-a-thousand-cuts than one-big-immovable-blocker that makes it hard to get stuff one. I've experience this with other frameworks and your description illustrates familiar difficulties. I am no longer curious about making an Android app to better understand the headaches. Thanks for saving me from that :-)
- allo37 6y agoWell I hope I didn't dissuade you from making an Android app at all! I've always hated the steady stream of discouragement that comes out of people who claim to "know better" and I'd certainly hate to have added to the pile. I'm just venting my frustrations after having developed a decently complex Android app for the past 1.5 years or so.