Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Cocoa Touch apps (2007)

twitter.com

Post reply on HN
Print view View original

51–60 of 78 posts

Re: Cocoa Touch apps (2007)

#51

Post by dkarras »

kevincox wrote: post #34
dkarras wrote: post #22

Earlier quoted context omitted.

And it just... sucks. So many avenues for exploitations for average developers that I'd never trust and install a 3rd party app on such a device that I carry around with me every day. Sure, Apple model is far far from perfect but the only solution I can think of for such a personal device.

> I'd never trust and install a 3rd party app on such a device that I carry around with me every day. I don't run any third party apps either. But I like that I am welcome to do so. In the past I have installed apps from third party developers that I trust and am the better for it.

I want to install apps though (and I actually do). Just those that makes economic sense for developers so that they won't want to resort to scams and even if they decided to, they wouldn't be able to. Apple's ecosystem provides that. I do run 3rd party apps on my Apple mobile devices and accept that there are reasonable vetting procedures at the human and OS level to protect my privacy and protect my device from malware. Android model unfortunately does not provide that, that's why I wouldn't install such apps in such a device.

Re: Cocoa Touch apps (2007)

#52

Post by atonse »

aaronbrethorst wrote: post #7

I just realized that more time has elapsed since the iPhone launched (about 14 years: 2007 - 2021) than had between when Jobs returned to Apple and the iPhone launched (about 11 years: 1996-2007). Yikes. Also, the three month deadline helps explain why the iPhoneOS SDK was such a mess when it first launched.

Also didn’t they debut it in the spring either way? I remember something like that. Or maybe it was 2.0

Re: Cocoa Touch apps (2007)

#53

Post by thrower123 »

jeromegv wrote: post #21
mortenjorck wrote: post #10

"Let's protect the user, by keeping control of [...] which entities can distribute apps (implies: signing infrastructure, policies, etc...)" Imagine an alternate universe where this foundational goal of the iOS SDK was interpreted just a little more loosely, with something closer to MacOS notarization, and an App Store that had to compete just like the Mac App Store.

Easy to imagine it. It’s the google android play store situation.

At least it's not the Amazon store. That place is scary, not to mention derelict. My Kindle Fire probably needs a pi-hole in front of it to make sure it's not hitting anything other than the Kindle APIs...

Re: Cocoa Touch apps (2007)

#54

Post by giantrobot »

pier25 wrote: post #4

Jesus they had 3 months to do it.

I was at Apple in SWE at the time.

While three months for public APIs was a tight schedule, a lot of the frameworks already existed and it was shoring up public access to them. Apple tends to dog food their own stuff for a while before making it public. The iOS 1 apps were using common APIs even if they weren't public.

The early iOS APIs were pretty limited and were typically a subset of everything in a framework. Subsequent releases added to public APIs or released new revamped APIs for the same purpose.

So it's not like Jobs was asking for years worth of work in three months, maybe just six months of work in three months.

Re: Cocoa Touch apps (2007)

#55

Post by afro88 »

The most amazing part of this for me is the goals were set before they started, and they delivered on them. The goals didn't change, they didn't pivot, it didn't agile it's way slowly into something else.

Clear vision, and what they delivered took over the world.

Re: Cocoa Touch apps (2007)

#56

Post by asddubs »

dkarras wrote: post #22
jeromegv wrote: post #21

Earlier quoted context omitted.

Easy to imagine it. It’s the google android play store situation.

And it just... sucks. So many avenues for exploitations for average developers that I'd never trust and install a 3rd party app on such a device that I carry around with me every day. Sure, Apple model is far far from perfect but the only solution I can think of for such a personal device.

Hard disagree. First thing I do on any new android phone is install a third party app: f-droid. the play store is impossible to navigate because it's flooded with ad-laden crap and overly permission-greedy dodgy apps. f-droid (for those who aren't familiar, it's an app store for open source applications) is an excellent way to get away from that and get apps that are basically guaranteed not to be user-hostile.

not to mention that app stores impose censorship on the sites that offer apps there. if you're an art platform you aren't allowed to show anything that even just vaguely hints at nudity (and I'm not talking about just outright porn here)

Re: Cocoa Touch apps (2007)

#57

Post by Wowfunhappy »

jjice wrote: post #43
doteka wrote: post #23

Earlier quoted context omitted.

Don’t think that’s as much a “Jobs” reply as just a general senior management necessity. With the amount of “important” emails you get in a position with any kind of responsibility, writing thoughtful elaborate responses to each and every one would leave you with no time to do your actual job. So you communicate the core message clearly and bluntly, and move on to the next fire.

I've grown to really like short responses, assuming they give enough info to answer the question. I think that a lot of us run into a subconcious thing where we feel like we need to say more, but most of the time we won't. I've been practicing recently, and it makes things so much faster and less tedious. I think I originally picked this up from professors, because I'd write a well thought out response (an unreasonab…

Jobs's reply in this case, however, was characteristically asshole-ish, not merely curt.

Re: Cocoa Touch apps (2007)

#58

Post by BuyMyBitcoins »

jjice wrote: post #43
doteka wrote: post #23

Earlier quoted context omitted.

Don’t think that’s as much a “Jobs” reply as just a general senior management necessity. With the amount of “important” emails you get in a position with any kind of responsibility, writing thoughtful elaborate responses to each and every one would leave you with no time to do your actual job. So you communicate the core message clearly and bluntly, and move on to the next fire.

I've grown to really like short responses, assuming they give enough info to answer the question. I think that a lot of us run into a subconcious thing where we feel like we need to say more, but most of the time we won't. I've been practicing recently, and it makes things so much faster and less tedious. I think I originally picked this up from professors, because I'd write a well thought out response (an unreasonab…

I forget which Apple engineer posted this anecdote, but Steve Jobs threatened to fire him and he agonized over a detailed response email.

But he ultimately just sent something like “Steve, you know how I feel. But you’re the boss. Let me know tomorrow if I’m fired or not”. He never heard back and just kept working at Apple.

Now I personally think the engineer’s like-kind response is probably what let him keep his job. But there’s something elegant about straightforwardness like this.

Re: Cocoa Touch apps (2007)

#59

Post by Wowfunhappy »

jeromegv wrote: post #21
mortenjorck wrote: post #10

"Let's protect the user, by keeping control of [...] which entities can distribute apps (implies: signing infrastructure, policies, etc...)" Imagine an alternate universe where this foundational goal of the iOS SDK was interpreted just a little more loosely, with something closer to MacOS notarization, and an App Store that had to compete just like the Mac App Store.

Easy to imagine it. It’s the google android play store situation.

That's completely different. Apple could protect users with an awesome curated app store, but still allow sideloading if desired. In fact, maybe with slightly lower volume they could have human reviewers actually spend more than 30 seconds per app.

Re: Cocoa Touch apps (2007)

#60

Post by Wowfunhappy »

asddubs wrote: post #56
dkarras wrote: post #22

Earlier quoted context omitted.

And it just... sucks. So many avenues for exploitations for average developers that I'd never trust and install a 3rd party app on such a device that I carry around with me every day. Sure, Apple model is far far from perfect but the only solution I can think of for such a personal device.

Hard disagree. First thing I do on any new android phone is install a third party app: f-droid. the play store is impossible to navigate because it's flooded with ad-laden crap and overly permission-greedy dodgy apps. f-droid (for those who aren't familiar, it's an app store for open source applications) is an excellent way to get away from that and get apps that are basically guaranteed not to be user-hostile. not t…

And you're able to install f-droid because Android allows sideloading, which has nothing to do with the awful way Google has managed the play store!
Post reply on HN