Just talking about the iPhone, there is an API that I’d like to see and I’m sure many applications would benefit from: A download manager. I imagine that an app could register to pull the content of a specific URL or the answer from a Web Service at a specified time or at specified intervals, and then the answers or most recent answer is ready for consumption when the app is started by the user.
Ideally, this would integrate with iTunes so that when syncing the phone, all the data-hungry apps get their mouths fed and are provided with the last version of the data they’re interested in. What I have in mind are news-plucking applications like All Things Digital or Bloomberg, or the TV schedule apps — or many of the other apps that you start, then wait to have their content pulled, and only then continue to use. The basic thing they do is simple: They all get their data in first. And I presume many, many of them in one or the other kind of XML application.
Man, would that improve my user experience of the iPhone.
Some thoughts on Apple’s answer to the FCC
August 26th, 2009Reading Apple’s public answer to the FCC’s questions, I cannot but notice a few very specifically worded parts of the answer that I’d like to highlight.
(Emphasis mine.) It may be that Apple provides us with the software they use themselves, but not with the APIs. In fact, quite a few interesting bits of the iPhone are not available to the iPhone developer who decides to pursue the Apple-authorized way only. Reports of things not being available are online aplenty, but let’s just mention tasks or applications running in the background, modifying the camera dialog or being able to add functionality to the settings dialogs used by Apple’s Settings app that developers are expected to hook into.
Yes, indeed. This was an industry first – that this freedom lie at the discretion of Apple, and not just be a transaction solely between the user of the device and the software developers. If a software company decided to develop for, say, the Palm Treo, they could just do that and offer their software for users of that plattform. If a company decided that developing for Symbian was something they’d like to do, they could just do that. Same for Blackberry and Windows Mobile.
Don’t get me wrong: I do understand that this is a double-edged sword. No other plattform has made it so easy for users to get software onto their devices; I do believe that the App Store is one of the cornerstones of making development for mobile platforms a viable business model. That’s one reason why the shortcomings of the App Store process are so irritating – because things could be even more fun for developers, now that the idea of developing for the iPhone fulltime isn’t so far-fetched anymore.
And I’m not even mentioning that as a customer of T-Mobile and as a german iPhone developer, I’m not sure why I even should care about the contract Apple has with AT&T. But this is not part of an investigation of the FCC.
(Emphasis again mine.) Well, I find that hard to believe. From my understanding of the technologies involved, there is no way that Google Voice could be replacing any functionality on the iPhone. They may be offering an application that offers similar or equal functionality — but it’s hardly a novel idea that companies would come in and offer software that does the same thing as an already existing piece of code, only potentially better — or rather, more in line with what the users expectations and needs are. If that’s what the users want, Apple would be well-advised to listen. And if the users find the experience too confusing for their own good or plainly do not like the application, no interest in it will happen anyway. I think that’s what’s called a market economy.
But it brings us around to the point from above: Even though the tools Apple offers are the same they use, there’s a strong distinction of what the independent developer is allowed (or able) to do, and what they themselves do. There is, for instance, no way of answering a phone call programatically on the iPhone, and I’ve got at least two ideas for applications that would be doing that. Or filter out types of SMS that get routed to an application, which would then act on them. Heck: I’d just like to be able to get an application to be started at a specific time of day, reliably.
I’m taking one app out of that list: GV Mobile. It’s developer, Sean Kovacs reports differently. It also has not rejected GV Mobile; it had approved it and suddenly pulled it from the App Store, with some warning in advance to the developer. This, to me, is not “continuing to study it.” Of course, it’s also not rejecting it — because it had been approved.
I’m not sure what to even make of this paragraph. Are they trying to tell us they do not know how Google Voice works? Or that their examination of the app has not even reached a state where they would be likely to … try out how it works? From my understanding of what I read online, it should not be hard to figure out that the app does not use VoIP over 3G — and there’s always the possibility of actually asking the developers how their app functions. But this paragraph alone does not instill trust into the approval process with me.
But let’s see what comes of all this. Maybe Apple will improve the quality of the review process, as they say they’re planning to.
No comments »
Posted in General
Tags: apple commentary iphone