Originally Posted by emmanuelbuah
Yes it is that simple if you plan ahead and they did not. Like you said, it was not meant to be a business phone. Actually, I really rather Apple not try to make it into a business phone because they are bad at it. Good at marketing but bad in business vision. I say the good and the bad as I see it. With that said, I like apple's strenghts (UI, uniformity etc) and hate their weakness ([their ego] failure to involve the dev ecosystem etc). They always wait till there is competition and not when the supporting community suggests/needs it. That's my bottom line.
Apple isn't "bad" at it. They're new to it. Apple hasn't been interested in larg businesses, and small one have different needs and concerns. Apple has been good there, while ignoring big business, because they weren't, and didn't want to be set up to deal with that.
This could be changing, because even big business is placing more Apple equipment in their environments than they have in a long time.
Apple hasn't been interested in helping them do that, which is why you think that they are bad at it. You cant be bad at something that you are avoiding doing at all. The most they've done is to make concessions on interoperability at the OS level, which has been getting better over time.
As for the ver 2 phone OS, it's much more business friendly than was ver 1. As a result, may commentators have said that for most businesses, thought not all, it is enough to get them in.
I've no doubt that as Apple has seem the light here, ver 3 will be friendlier yet. It's interesting that in the last big survey, the iPhone was given much higher ratings from business customers in every area that was given the Blackberry. That says something interesting. It says that even with a possibly "half finished" product, it beat out the otherwise most highly thought of product in the business category.
You have to think of that as well.
Now if you think I'm complaining about signing up before reading what an sdk can do, then you have been an apple cheerleader for far too long. An sdk documentation helps someone to better make a decision if their app will be supported by the api's provided by the platform. Now, signing up and finding out that my app cannot be supported on the iphone because it needs a background process is sheer stupidity and wast of my time and an extra account someone else doesn't need. In my case, i compromised and degraded my app to fit the iphone eco apps but still stupid if you ask me.
Please don't call people cheerleaders, fanboys, etc. It gets in the way of intelligent conversation. I respect your views in this even if I don't agree with them, and I expect you to respect mine as well.
I understand what an SDK is for, and I understand what the documentation is for as well. I also understand that signing up for it is not a big deal.
What app did you write BEFORE you signed up for the SDK and received the information and software required for writing it?
If this was all a waste of your time, why did you bother to do it? I don't understand that.
If all you had was an idea for an app first, then you didn't have much.
Are you also planning to write this app for the Android? That's about as open as you can get right now.
If you do, then let us know about the process.