"I was merely a web developer, not an iPhone developer"
Thinking that alone is a mistake -- there is nothing magical about iPhone developers, and ios programming can be learned quickly. If you're doing a startup, you can't believe anything other people are doing is impossible to master.
(that may very well be the case, but it always warrants investigation)
That's not really true. For the most part (no, this isn't true everywhere, but for the most part), the tolerances are a lot looser in web development, in pretty much all areas. Unless you're getting pummeled on inadequate hardware, your performance choices in the backend of a web site or web app are probably going not going to harm anything.
If you make bad performance choices on an iOS application, you'll create a stuttery, ugly mess (smooth scrolling in an iOS application is surprisingly nontrivial) that will--unforgivably--sap a user's battery and ruin their experience.
People are a lot more forgiving of 2ms greater response time on a web page than a web app that drains 4% of battery in five minutes.
Yes, even if it gets the job done. Because if it gets the job done poorly, by causing significant battery drain or performance problems or other hallmarks of bad code, you are mistreating your users.
Novice code isn't necessarily imbecilic code, you're conflating the two. If I'm otherwise proficient and have a grasp of hardware conceptually, my iOS code isn't likely to do those things you stated.
Comments
"I was merely a web developer, not an iPhone developer"
Thinking that alone is a mistake -- there is nothing magical about iPhone developers, and ios programming can be learned quickly. If you're doing a startup, you can't believe anything other people are doing is impossible to master.
(that may very well be the case, but it always warrants investigation)
That's not really true. For the most part (no, this isn't true everywhere, but for the most part), the tolerances are a lot looser in web development, in pretty much all areas. Unless you're getting pummeled on inadequate hardware, your performance choices in the backend of a web site or web app are probably going not going to harm anything.
If you make bad performance choices on an iOS application, you'll create a stuttery, ugly mess (smooth scrolling in an iOS application is surprisingly nontrivial) that will--unforgivably--sap a user's battery and ruin their experience.
People are a lot more forgiving of 2ms greater response time on a web page than a web app that drains 4% of battery in five minutes.
No one is born writing elite code, and the question is one of overcoming fear to conquer new ground, even if modestly at first.
Yes, but subjecting other people (especially paying ones) to your novice code is kinda iffy.
Not if it gets the job done.
Yes, even if it gets the job done. Because if it gets the job done poorly, by causing significant battery drain or performance problems or other hallmarks of bad code, you are mistreating your users.
Novice code isn't necessarily imbecilic code, you're conflating the two. If I'm otherwise proficient and have a grasp of hardware conceptually, my iOS code isn't likely to do those things you stated.
(signout from subthread)