4 ms·

"Apple did not want to allow native apps on the iPhone, and was pushed into it by the overwhelming strength of the jailbreak community. People wanted the better

by Hisoka 15y ago

"Apple did not want to allow native apps on the iPhone, and was pushed into it by the overwhelming strength of the jailbreak community. People wanted the better user experience provided by native apps, and if Apple wouldn't allow it, they would do it themselves." Maybe I'm ignorant.. but how is this true? Apple could have NOT release the API for creating iPhone apps, and there wouldn't be any iPhone apps. You can crack, jailbreak, hack, and hax0r all you want. No API, no native app.

recoiledsnake 15y ago
There is always an internal API or even kernel level functions that can be used. Of course, they may break in the next update but you can use the same way of reading input, displaying graphics, getting device location as, say the mail client and Maps.
Wilya 15y ago
Remember the iPhone is, inside, a Darwin system. Put a terminal, and the sky is the limit. Plus, there is always an API. The API, in the first days, wasn't public, but it was there. The base apps included (calendar, browser, etc) needed it. And there was an app store (well, a fully free store) before Apple even released their APIs. I don't know how people discovered the APIs (reverse-engineering ? Leaks from Apple ?), but they had them.
geon 15y ago
There was several native apss written before thte SDK was released. The game Trism was one of them. I still don't believe Apple "was pushed into it by the overwhelming strength of the jailbreak community". Apple must have had it planned, even before the SDK and the Appstore infrastructure was ready. The web app-only strategy was retarded; no one wanted that, and Apple knew it. Still, consumers would never accept the walled garden model if it was enforced after native apps were allowed. Web apps were only a surrogate until the Appstore was ready, but they couldn't market it like that, could they?

by Hisoka 15y ago

recoiledsnake 15y ago

There is always an internal API or even kernel level functions that can be used. Of course, they may break in the next update but you can use the same way of reading input, displaying graphics, getting device location as, say the mail client and Maps.

Wilya 15y ago

Remember the iPhone is, inside, a Darwin system. Put a terminal, and the sky is the limit. Plus, there is always an API. The API, in the first days, wasn't public, but it was there. The base apps included (calendar, browser, etc) needed it. And there was an app store (well, a fully free store) before Apple even released their APIs. I don't know how people discovered the APIs (reverse-engineering ? Leaks from Apple ?), but they had them.

geon 15y ago

There was several native apss written before thte SDK was released. The game Trism was one of them. I still don't believe Apple "was pushed into it by the overwhelming strength of the jailbreak community". Apple must have had it planned, even before the SDK and the Appstore infrastructure was ready. The web app-only strategy was retarded; no one wanted that, and Apple knew it. Still, consumers would never accept the walled garden model if it was enforced after native apps were allowed. Web apps were only a surrogate until the Appstore was ready, but they couldn't market it like that, could they?