Yes, but what limitation of the keyboard would a developer need to use private APIs in order to get around? What would Arumugam want his Economy tracking application to do that can't be done with the keyboard as is?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Steve Jobs Phones Developer of Rejected iPad Application
- Thread starter MacRumors
- Start date
- Sort by reaction score
Yes, but what limitation of the keyboard would a developer need to use private APIs in order to get around? What would Arumugam want his Economy tracking application to do that can't be done with the keyboard as is?
If you follow through with the links, you will get to the developer's blog:
http://blog.cascadesoft.net/2010/10...from-steve-jobs-and-the-economy-for-ipad-app/
Essentially, the keyboard would stay stuck in certain situations with no possibility for the user to dismiss it.
Im amazed at how asinine smart people can be. how in the world did this developer expect to get an app approved when it uses a private API? im not even a programmer yet i know that private API's are forbidden.
Lame.
Lame.
Its lame because Steve shouldn't have to hold the developers hand and baby sit this guys emotions. the developer was crying about the rejection of their app, but they put a freaken private API in the mix. Steve Jobs literally held this jokers hand and spelled it out for him. What a waist of time. If the guy doesnt know the BASIC rules, he shouldnt be developing.
Sure, it was kind of Steve, but it wasnt necessary and I for one wouldnt buy this guys app because of his complete lack of attention. this is good PR for apple though. it just bugs me that a developer would put in a private API then whine when the app is rejected (even if that private API was to fix some sort of bug).
Last edited:
Is the world black and white for you? The developer was trying to work around what he believed to be a iPad SDK bug.
For all the noise and Steve talk - Apple didn't actually fix the SDK bug but made the developer rewrite a portion of his app to work around it - that's asinine.
Not really. CEOs in most large companies often become completely out of touch with customers and partners, even employees. I'm impressed Steve is smart enough to reach out directly, deep into the Apple ecosystem. I'm sure he gained some insights into the concerns of this particular developer, and by extension, the entire developer community.
huh? private API's wont pass. thats the point. get it? if the developers intention was to use the private API to remedy the bug would it not make sense to ask apple for this exception to the rule instead of initiating, submitting, then whining about it when they refuse?
Pressure
I guess the Android pressure is mounting. He does not want to lose even a single developer.
I guess the Android pressure is mounting. He does not want to lose even a single developer.
And who would get blamed when the next version of iOS broke the private API, and the app stopped working?
As much as I adore the "public API hugging" - if the public APIs are not doing the job, resulting in people needing to use private ones just to get their app working - Apple should show some respect, fix the root cause - bug in public API - and then ask developers to remove the private API.
Does Steve do much at apple anymore? No wonder they only pay him a dollar a year he's just answering his email
Where did you get that from? If you watched the All Things D D8 conference where Walt and some other person interviewed Steve Jobs he gave a brief explanation of what he does at Apple; and it's certainly not just answering e-mails.
Because some people just have to be like that in these sorts of threads for no valid reason. I agree with what you said though, it's great that Steve called the developer to help the guy understand the company's position on the use of private APIs.
Last edited:
well sure. I think your right. however, a developer cant expect apple to change policy just for him without discussing the situation before hand. point is, the dev knew he was breaking the rules and that the app wouldnt get approved, yet cried fowl when they rejected it. that just doesnt make sense.
i agree, apple should fix any bugs. im sure the bug is now on a fix it list if it wasnt already.
The developer's account leaves out a few key details. After his conversation with Jobs, he resubmitted his app with a workaround that avoided the buggy pubic API. How come he didn't find this workaround before he talked to Jobs? Did something Jobs said help him find this workaround, or was he simply too bullheaded before his chat with Jobs to search for alternative ways around his problem?
Yeah, which is sort of interesting, because a) Apple reportedly uses those private API themselves and b) when Microsoft did it, they were sued to Kingdom Come.
I think Albert Einstein was the first one to become famous for only having one kind of dress: He had a wardrobe full of the exactly same type suit because he didn't want to waste a thought on what he was going to wear this day.
I adopted this attitude myself: I have dozens of the same black T-Shirts and black Sweat Shirts. But since it dawned on me that Apple's ad slogan should really be "Conform Always", I no longer wear my Think Different T-Shirt...
Impressed!!!!
How many CEOs would PERSONALLY call in a situation like this?
Ballmer? HA HA HA!!!!!
Kudos to Steve for 1) calling and 2) for working things out with the guy.
And yet the trolls will put a negative spin on it....it is just who they are.
How many CEOs would PERSONALLY call in a situation like this?
Ballmer? HA HA HA!!!!!
Kudos to Steve for 1) calling and 2) for working things out with the guy.
And yet the trolls will put a negative spin on it....it is just who they are.
Not a developer here....however, I do have some experience with staff hierarchies. My guess is that someone flagged the email for Jobs. Maybe at the same time brought in an Apple developer to look at the app - perhaps the same one who is/will be looking at the supposed bug.
Jobs would have been briefed by the Apple developer, who would have made themselves familiar with the proposed app. They likely would have pointed out the workaround - and Jobs would have then called the app's developer, explained company policy, and then mentioned the suggested workaround.
Jobs does not need to know how every single thing at Apple works, but he will have a really good briefing before venturing into anything.
I wonder if the app is considered to be otherwise a shining example of what Apple would like to see, so that extra effort was made to keep the developer happy.
+100
You don't see Michael Dell or Steve Ballmer doing that.
This says volumes about how much Steve cares about the products they make and the customers that use them. Remember, without the customers, you're nothing.
Whether it is an actual keyboard API bug or just a layout that makes manipulating statistics programs difficult, I would not be at all surprised if Apple updates the API to address the concern. The program looks worthy and is clearly in the range of apps Apple wants in the ecosystem.
All this publicity will certainly spike sales of the app of course.
Steve has planted his flag on this hill.
Rocketman
All this publicity will certainly spike sales of the app of course.
Steve has planted his flag on this hill.
Rocketman