Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Four? I need my three-inches update.

3inches.jpg
 
Really, more people need to learn basic programming so these questions will disappear. In addition to that, it'll help you get good paying jobs.

You want people to learn basic programming so that they don't ask these questions? Talk about overkill!

I would consider while loops to be a basic fundamental aspect of programming, yet if you try explaining that to somebody that's never looked at programming before their head will explode :p
 
The only reason my app is not yet iPhone 5 compatible is because I'm working on a big update and I don't have a branch for the older version. I don't want to submit a half-finished update.
 
Just because you don't see a lot of work, doesn't mean there isn't a lot of work.

I do some programming for iOS. I'm not very good at it tbh but I don't see myself needing more than a week to update an app like whatsapp. I'm sure a game needs a lot of work, but not whatsapp. And I bet they have more than one programmer and all of them are way better than me.
 
and all of them are way better than me.

That's why it will probably take them longer.

I found it easier and faster to complete projects when I first started out. As a noob, you don't bother planning anything, you just get stuck in and do it.

When you progress and learn about more advanced programming, you need to plan more and sometimes writing code becomes more longwinded if you want to be able to extend your program later, for example.

Do you just want your program to do one thing and that's all it will ever do, or do you want to be able to easily extend it?

Also, as a noob you use silly variable names like "a" or "b," but when you work on a large project you realise the importance of sensibly named variables. Trying to find out what "a" is in a 100,000+ line source file is a nightmare.
 
That's why it will probably take them longer.

I found it easier and faster to complete projects when I first started out. As a noob, you don't bother planning anything, you just get stuck in and do it.

When you progress and learn about more advanced programming, you need to plan more and sometimes writing code becomes more longwinded if you want to be able to extend your program later, for example.

Do you just want your program to do one thing and that's all it will ever do, or do you want to be able to easily extend it?

Also, as a noob you use silly variable names like "a" or "b," but when you work on a large project you realise the importance of sensibly named variables. Trying to find out what "a" is in a 100,000+ line source file is a nightmare.

I get your point but I maintain what I said. Whatsapp isn't a difficult app to update for a 4" display. Maybe they're planning a whole new redesign and to include more options, who knows... But just stretching the app is super simple for a team of devs like theirs and for an app like whatsapp!
 
I get your point but I maintain what I said. Whatsapp isn't a difficult app to update for a 4" display. Maybe they're planning a whole new redesign and to include more options, who knows... But just stretching the app is super simple for a team of devs like theirs and for an app like whatsapp!

With all due respect you can't possibly say that without seeing the code/project/graphics involved.
 
Hmm, i'm not sure I agree with the comment about people needing to learn basic programming skills so that these sort of questions don't get asked. There will always be users, and they will always ask these sort of questions. And so they should!

Personally, i don't mind answering them on a forum like this. What really frustrates me is direct emails / support requests for new features. All that does is lessen the amount of time I can work on the features, because i spend it replying to the support requests. If i don't reply, the apps get bad ratings, etc etc... It's kinda a vicious circle.

I'm also not sure anyone can say, 'surely it's not that hard to do this app or that app'... You'd be very surprised at what goes on behind the scenes of some Apps. A good analogy would perhaps be the Wizard Of Oz (Man behind the curtain.)

Some App developers (myself included) back at the beginning never planned far enough into the future to consider different screen resolutions. So a lot of graphical elements may have hard coded pixel position values, this then becomes not only a graphical element change, but also there is some significant dev work to be done here too, there are two options to consider...

1. Implement a switching based system and figure out all the new hard coded values for the 4" screen size... (NOT THE RIGHT THING TO DO)

2. Or you spend some time getting to know Apples new auto-layout system and implement that into your App, meaning any future resolution changes will be almost seamless. This is the right thing to do, but this will take a significant amount of time.

The whole issue of hard coding pixel positions for elements adds another level of complexity when you consider animations (I'm talking even basic slide in / slide out stuff here), it's highly likely that if graphical elements positions were hard coded, any animations that applied to them would also have hard coded position values, it's likely these will all need to be changed for a 4" screen size too. Just because something looks like it could just be stretched down the screen (WhatsApp is a prime example) don't presume that it'll be that easy.

Whilst Apps like WhatsApp may seem like they have a whole hoard of developers behind them... often you'll find it's just one or two developers, rushed off their feet with several other projects on the go and deliverables to meet. It's unfortunate that not every company / developer can drop everything for a 2 week period when Apple releases a new version of iOS (or OS X for that matter) but that's the way it is i'm afraid.

Finally, don't forget it's not just the 4" screen developers have to make changes to support. iOS 6 itself introduced some pretty significant changes for developers, and i'm sure some devs are still putting the finishing touches onto iOS 6 compatible updates (let alone iPhone 5 compatible.) Remember, we only got a week with the GM build before iOS 6 went live, and with the best will in the world, that's not long enough to test all the iOS 6 changes whilst simultaneously updating the App for the new screen size Apple dropped on us. Personally I went with a two tier approach, the iOS 6 updates for my apps were released on the day iOS 6 went live, and the final touches are being put on the iPhone 5 interfaces now, I think my users would rather have an app out there that doesn't crash on iOS 6 before having an app that looks great on the new iPhone.

Again, i'm open to discussion, just giving you my thoughts as a dev...
 
I was surprised new games like Bad Piggies from Angry Bird makers didn't launch with iPhone 5 screen size resolution.
PJ
 
I was surprised new games like Bad Piggies from Angry Bird makers didn't launch with iPhone 5 screen size resolution.
PJ

This game will have been in development a long time before iOS 6 and iPhone 5 was announced.
 
You want people to learn basic programming so that they don't ask these questions? Talk about overkill!

I would consider while loops to be a basic fundamental aspect of programming, yet if you try explaining that to somebody that's never looked at programming before their head will explode :p

Learning programming should be like learning English or any of the major world languages. If you don't know anything about programming in today's society, you're putting yourself at a disadvantage. In addition to learning how to create something, programming helps you learn logic, the process, and how to solve problems.

If while loops make non-programmers' heads explode, imagine how programmers feel when non-programmers ask why things aren't fixed instantly the second a new piece of device comes into the market. That makes our heads explode.

----------

Hmm, i'm not sure I agree with the comment about people needing to learn basic programming skills so that these sort of questions don't get asked. There will always be users, and they will always ask these sort of questions. And so they should!

Personally, i don't mind answering them on a forum like this. What really frustrates me is direct emails / support requests for new features. All that does is lessen the amount of time I can work on the features, because i spend it replying to the support requests. If i don't reply, the apps get bad ratings, etc etc... It's kinda a vicious circle.

I'm also not sure anyone can say, 'surely it's not that hard to do this app or that app'... You'd be very surprised at what goes on behind the scenes of some Apps. A good analogy would perhaps be the Wizard Of Oz (Man behind the curtain.)

Some App developers (myself included) back at the beginning never planned far enough into the future to consider different screen resolutions. So a lot of graphical elements may have hard coded pixel position values, this then becomes not only a graphical element change, but also there is some significant dev work to be done here too, there are two options to consider...

1. Implement a switching based system and figure out all the new hard coded values for the 4" screen size... (NOT THE RIGHT THING TO DO)

2. Or you spend some time getting to know Apples new auto-layout system and implement that into your App, meaning any future resolution changes will be almost seamless. This is the right thing to do, but this will take a significant amount of time.

The whole issue of hard coding pixel positions for elements adds another level of complexity when you consider animations (I'm talking even basic slide in / slide out stuff here), it's highly likely that if graphical elements positions were hard coded, any animations that applied to them would also have hard coded position values, it's likely these will all need to be changed for a 4" screen size too. Just because something looks like it could just be stretched down the screen (WhatsApp is a prime example) don't presume that it'll be that easy.

Whilst Apps like WhatsApp may seem like they have a whole hoard of developers behind them... often you'll find it's just one or two developers, rushed off their feet with several other projects on the go and deliverables to meet. It's unfortunate that not every company / developer can drop everything for a 2 week period when Apple releases a new version of iOS (or OS X for that matter) but that's the way it is i'm afraid.

Finally, don't forget it's not just the 4" screen developers have to make changes to support. iOS 6 itself introduced some pretty significant changes for developers, and i'm sure some devs are still putting the finishing touches onto iOS 6 compatible updates (let alone iPhone 5 compatible.) Remember, we only got a week with the GM build before iOS 6 went live, and with the best will in the world, that's not long enough to test all the iOS 6 changes whilst simultaneously updating the App for the new screen size Apple dropped on us. Personally I went with a two tier approach, the iOS 6 updates for my apps were released on the day iOS 6 went live, and the final touches are being put on the iPhone 5 interfaces now, I think my users would rather have an app out there that doesn't crash on iOS 6 before having an app that looks great on the new iPhone.

Again, i'm open to discussion, just giving you my thoughts as a dev...

Your entire post contradicts your first sentence. I'm not saying everyone needs to learn how to do iOS programming. My point is they should all learn how to write something and at least get a feel of the process and the challenges involved. Looking at your long vent, it seems like if users learn the process, even the basics, it would help a lot in not wasting your time with dumb questions.

Also, if more people knew how much effort it took to build these things, maybe less people will pirate/hack these programs - but that's another debate for another day.
 
Learning programming should be like learning English or any of the major world languages. If you don't know anything about programming in today's society, you're putting yourself at a disadvantage. In addition to learning how to create something, programming helps you learn logic, the process, and how to solve problems.

If while loops make non-programmers' heads explode, imagine how programmers feel when non-programmers ask why things aren't fixed instantly the second a new piece of device comes into the market. That makes our heads explode.

Lots of people make it through lives, have families and very successful jobs without knowing squat about programming.

Programming is still very much a nerdy topic, the masses don't give a damn about it.
 
Learning programming should be like learning English or any of the major world languages. If you don't know anything about programming in today's society, you're putting yourself at a disadvantage. In addition to learning how to create something, programming helps you learn logic, the process, and how to solve problems.

If while loops make non-programmers' heads explode, imagine how programmers feel when non-programmers ask why things aren't fixed instantly the second a new piece of device comes into the market. That makes our heads explode.

----------



Your entire post contradicts your first sentence. I'm not saying everyone needs to learn how to do iOS programming. My point is they should all learn how to write something and at least get a feel of the process and the challenges involved. Looking at your long vent, it seems like if users learn the process, even the basics, it would help a lot in not wasting your time with dumb questions.

Also, if more people knew how much effort it took to build these things, maybe less people will pirate/hack these programs - but that's another debate for another day.

In your opinion obviously! :)
 
Lots of people make it through lives, have families and very successful jobs without knowing squat about programming.

Programming is still very much a nerdy topic, the masses don't give a damn about it.

The masses don't give a damn about lots of things and millions would prefer to keep up with the Kardashians and watch Honey Boo Boo than to contribute something positive to society.

Am I really supposed to live my life and educate my kids based on the low bar set by the masses?

----------

In your opinion obviously! :)

...and your opinion too. I don't see why you don't see it.

You said:

I don't mind answering questions except when people ask why isn't it done now, why they don't get this, they don't get that, etc.

So what you're basically saying is you DO mind answering stupid questions cause the general population doesn't get what you do.

I'm advocating the general population learn a tad bit about what you do so the stupid questions (your exceptions) go away.

Not sure why you're fighting it when I'm on your side.
 
The masses don't give a damn about lots of things and millions would prefer to keep up with the Kardashians and watch Honey Boo Boo than to contribute something positive to society.

Am I really supposed to live my life and educate my kids based on the low bar set by the masses?

----------



...and your opinion too. I don't see why you don't see it.

You said:

I don't mind answering questions except when people ask why isn't it done now, why they don't get this, they don't get that, etc.

So what you're basically saying is you DO mind answering stupid questions cause the general population doesn't get what you do.

I'm advocating the general population learn a tad bit about what you do so the stupid questions (your exceptions) go away.

Not sure why you're fighting it when I'm on your side.

As much as I'd like to agree I just can't. As a developer for about 2 decades I think that that would just be disastrous, in fact I think it would cause the opposite reaction compared to what you think. People should just understand that it isn't as easy as they think, but it's better off they stop right there.

When you start education someone to a very basic level they tend to cause more harm than good, what you end up with is people who have but a very basic grasp of the concepts and then spout off about how they could have made the change in X minutes because it's so easy. In reality complex apps are, as a result, complex to update or make changes to so it isn't nearly as quick. The only way from where we are now to where you want everyone to be is extensive education and experience on projects which just isn't going to happen. It's not too far from basic car maintenance, you should be able to top off your oil, but I don't think that that has more correlation to the complexity of a transmission rebuild, nor is that something that people should spend a lot of time learning.
 
I have no knowledge of how hard/easy it is to make an app compatible with the new iPhone 5's screen, but really how hard is it?

As a developer I will give you my perspective. It is really easy for apps like facebook, twitter, etc. This is because they use common design items but adapt them to their own needs (table controllers, navigation bars, etc). However games that use custom interfaces are going to be harder because they have to completely update the artwork, because it would be boring and look terrible if they just stretched things to meet the new aspect ratio
 
The masses don't give a damn about lots of things and millions would prefer to keep up with the Kardashians and watch Honey Boo Boo than to contribute something positive to society.

Am I really supposed to live my life and educate my kids based on the low bar set by the masses?

Are you implying that programming is the only way people can contribute to society? Sure seems that way...
 
Learning programming should be like learning English or any of the major world languages. If you don't know anything about programming in today's society, you're putting yourself at a disadvantage. In addition to learning how to create something, programming helps you learn logic, the process, and how to solve problems.

If while loops make non-programmers' heads explode, imagine how programmers feel when non-programmers ask why things aren't fixed instantly the second a new piece of device comes into the market. That makes our heads explode.

----------



Your entire post contradicts your first sentence. I'm not saying everyone needs to learn how to do iOS programming. My point is they should all learn how to write something and at least get a feel of the process and the challenges involved. Looking at your long vent, it seems like if users learn the process, even the basics, it would help a lot in not wasting your time with dumb questions.

Also, if more people knew how much effort it took to build these things, maybe less people will pirate/hack these programs - but that's another debate for another day.
It's totally not necessary.

Your entire premise that it's bad for people to ask questions is bad and unhealthy.

I know many very intelligent, productive people from police officers, medical professionals, microbiologists, construction workers who are highly skilled in their own roles but are completely computer illiterate.

As you grow up, and meet more people, you'll learn that everyone is unique and doesn't have to confirm, and that your interests have a very narrow breadth on the grand scheme of the world.
 
It's totally not necessary.

Your entire premise that it's bad for people to ask questions is bad and unhealthy.

I know many very intelligent, productive people from police officers, medical professionals, microbiologists, construction workers who are highly skilled in their own roles but are completely computer illiterate.

As you grow up, and meet more people, you'll learn that everyone is unique and doesn't have to confirm, and that your interests have a very narrow breadth on the grand scheme of the world.

Exactly what I'm trying to say - people can live very fulfilling lives and have skilled jobs without knowing anything about programming.

I work with a bunch of lawyers and they know almost nothing about computers, but are solicitors with 20+ years experience :p
 
From a developer's standpoint:
- it should be fairly easy to adjust an utility app for larger screen, because you basically place you widgets on more spaces, either move or enlarge them. I updated my QEver note several days after iPhone 5 release.
- for games, it would be harder, because larger screen can mean completely new game play experience, and requires design and graphics and programming change.

So give games some more time; but for utility apps, they should already have done that.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.