Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
You can still find apps that haven't been updated since 2010 or 2011. Apple needs to do a better job at pruning the App Store. That 1.3 million app figure is pretty pointless when 500,000 of them are crap anyway.
This. Some of the games I downloaded a few years back are still calibrated to my iPod touch.
 
The issue is that you can only charge customers once. I stopped supporting Battery Status when it stopped having 5 downloads a day because it was no longer worth my time to do so (you're asking me to keep working for $7/day? Not happening.) I pulled it off the store.

If we were allowed to charge for updates, or if customers would accept reasonable prices ($1? Ad supported? What a freaking joke.) then we could offer more support. As is, it's not worth it at all.

I'm a PC and console game developer, maybe I just love my games and name more but I've supported them out of my own pocket when needed ;). I just updated a game I made in 2010 with support for new controllers, new controller tech and some optimisations I found along the way. I'm not "hand to mouth" though and I know app development can be kinda tight.
 
So wait... This is only happening NOW? Apple DIDN'T move the phone ecosystem to 64 bit in one day like they said? Like they said when they mocked how the computer industry took years? Choke on your hyperbole Phil Schiller.

“The PC world made the transition from 32-bit to 64-bit, and it took years. Today, you’re going to see that Apple is going to do it on one day,” Schiller said.

Meaning, I've been having low memory app crashes the last year because this SOB didn't keep his word.

Thanks Schit Philler.
 
Many of my favorite apps aren't being actively updated any more, because small developers tend to move on with their lives. These apps are often higher quality than 80% of the new apps. But all those crap apps you mentioned? They'll be replaced by 500,000 NEW crap apps, written and submitted even faster than before.

I do agree that "flushing" the App store is a good thing. I just don't think the best way to judge the merit of an App is how actively it's still being developed.

Yes, but there are clearly a multitude of apps no longer supported that have longs since lost their usefulness. Eventually an OS update will break even the good ones. Apple needs a way of, as you put it, flushing out those apps.
 
Yes, but there are clearly a multitude of apps no longer supported that have longs since lost their usefulness. Eventually an OS update will break even the good ones. Apple needs a way of, as you put it, flushing out those apps.

Why would they do that, though? They need to be able to say that you can access eleventy million apps because their OS is the best.
 
For 99% of apps, it's no extra work - you just set the compiler to be 32 bit and 64 bit, and it will work.

The only gotchas are if your code looks at 32 bit boundaries, or shifts bits, expecting certain answers. For example, if you're right-shifting 32 bits by one, expecting the '1' to hyperwarp over to the left, like this.... expecting 1 to turn into 4,294,967,296

00000000000000000000000000000001 = 1
10000000000000000000000000000000 = 4,294,967,296

but doing this on a 64 bit system does this:

0000000000000000000000000000000000000000000000000000000000000001 = 1
1000000000000000000000000000000000000000000000000000000000000000 = 18,446,744,073,709,551,616

Most apps don't care, and would never do any of this, but certain complex mathematical equations used in, for example, graphical processing applications might not work the same in 64 bit vs 32 bit

For my project, most of the work was compiler warnings on NSLog(@"%d", some_nsinteger);. Oh, and updating third-party libraries to more recent versions that do support it (without compiler warnings, that is).
 
A lot of people seem to be overreacting.

Apple cuts off old versions of Xcode all the time. This move doesn't exclude any more devices than any other Xcode cut-offs in the past.

Requiring 64-bit binaries does not exclude 32-bit binaries. Both binaries are included. Most of an app's size is not from the binary, but from other resources such as graphics or audio. A 10.25 MB download might jump to 10.75 MB.

Devices this new requirement will help:
* iPhone 5S
* iPhone 6
* iPhone 6 Plus
* iPad Air
* iPad mini 2
* iPad Air 2
* iPad mini 3

Device this new requirement will harm:
* none


A 64-bit device running a 64-bit app may end up with more available memory for that app since it does not have to load 32-bit libraries in addition to 64-bit libraries. Understand? Compiling with 64-bit support can make an old app run better.


OS X applications already included 32/64-bit binaries. In fact, many applications had both the PowerPC/Intel binaries ("Universal" binaries). No one complained then.

Apple isn't the only company that does this. Microsoft .NET compiles apps with native 32/64-bit support as well.
 
I can proudly say that the app I work on is ready. I had been pushing for this to the powers that be for a time when it was announced. Still not released, but no surprises come February.

And yes, I added support for iPhone 6/6+, although we don't have much @3x images at the moment. I'm no graphic artist...

Depends on the app.
Xcode 6 is a bigger headache than anything else. Apple loves to do undocumented changes and radically change how API work. This can break a lot of items.

For example they flipped how X,Y coordinates are reported. Same method call returns them flipped. You ask for the size of the screen it used to always be coordinates based in portrait so if you were doing landscape work you adjusted for that. Now it is reported based on the current ordination of the device. Breaks everything that relayed on that.

App my company makes Xcode 6 is looking at costing us a few weeks of dev time to redo a lot of stuff to make it complaint.

64 bit chances are it will be fine but really there are a lot of gotchas you never account for. You can only find by really doing deep test.
Translates in to thousands of dollars of time. Brings in Zero new money as it is just updating.

Short answer is if you are not doing anything crazy it is easy to upgrade. As soon as you start doing custom stuff a lot of problems and almost every app has some custom crazy work in it.
 
A lot of people seem to be overreacting.

Device this new requirement will harm:
* none
Ohh, really! :rolleyes:

If the frameworks of iOS 9 do not support 32-Bit apps (and they don't), then this is the end of 32-Bit apps on iOS iDevices-right here. I think this is where Android wins. Android apps run within a VM (similar to JavaScript in Safari (JIT-compiler))). Newest Android versions support many manufacturers of ARM chips and the OS and applications run on Qualcomm and Samsung processors and support ahead of time compilation (source).

iOS appears like a shadow of itself. Somehow washed-out and dying.
 
I thought this meant the end for the iPhone 5 since it's not 64-bit.
Then I realized what it actually said.

iOS 8 software development kit and INCLUDE 64-bit support

It does not say that it is ONLY 64-bit it says that 64-bit support is required for any new project. AKA 32-bit only versions are no longer accepted, without a 64-bit supported version too.

So I'm totally fine with it in that case :cool:
 
Ohh, really! :rolleyes:

If the frameworks of iOS 9 do not support 32-Bit apps (and they don't), then this is the end of 32-Bit apps on iOS iDevices-right here. I think this is where Android wins. Android apps run within a VM (similar to JavaScript in Safari (JIT-compiler))). Newest Android versions support many manufacturers of ARM chips and the OS and applications run on Qualcomm and Samsung processors and support ahead of time compilation (source).

iOS appears like a shadow of itself. Somehow washed-out and dying.

What? We know what the frameworks of iOS 9 support? Or are you an Apple employee that needs to be fired for leaking something big? :)
 
I upgraded my iphones (6, 5s, and 5c) and ipads (2 ipad air 2) this year. So I am 100% 64-bit. I know I am probably not the majority, so leaving 32-bit support for a while is probably smart. But in about 2 years (iOS 10) there should be no reason for 32-bit apps.

The next question is, when will 128-bit arrive?:D

The 5c is 32-bit.

Everyone saying that iOS 9 will only support 32-bit are forgetting the 5c. (And maybe the iPod Touch)
 
Absolutely agree.. It drives me up the wall to still see scaled apps, especially that many have been updates many times since iOS8 came out.

Maybe you should blame Apple for releasing new screen sizes every ****ing year instead of sticking with one or two. They're fragmenting their own market and the developers (myself included) cannot afford to continue playing cat and mouse with them.

But no, it's our problem, because we don't want to invest a couple thousand bucks (or more!) redoing all the graphics and UI layout for an app that only brings in a couple hundred a month.

-SC
 
So this means that unless an app is developed ONLY for a 64-bit chipset, that apps will take up twice as much space? A developer wishing that his apps can be used by people with 32-bit iDevices and also 64-bit iDevices can submit both binaries in one package, therefore an app that is ½ a gigabyte in size will become 1 gigabyte in size... wasting all that extra space on users' iPhones -.

Whoa... No, the actual executable code in an app only accounts for a small percentage of the total app size. You're only talking a few percentage points extra having both the 32 and 64 bit code in there.
 
If we were allowed to charge for updates, or if customers would accept reasonable prices ($1? Ad supported? What a freaking joke.) then we could offer more support. As is, it's not worth it at all.

As a non-developer, I have wondered how much a developer makes from ad supported apps. I paid $2.99 to upgrade from the Sudoko2 to Sudoko2 Pro... Just to remove the ads. I would think that if they offered this option, they must make less than $2.99 from the ads. Either way, seems people are not willing to pay hardly anything for apps any more. Lotta complaining about $5 apps!
 
Another reason why iOS apps are superior to Android apps: Apple forces devs to use the new technology.

----------

Maybe you should blame Apple for releasing new screen sizes every ****ing year instead of sticking with one or two. They're fragmenting their own market and the developers (myself included) cannot afford to continue playing cat and mouse with them.

But no, it's our problem, because we don't want to invest a couple thousand bucks (or more!) redoing all the graphics and UI layout for an app that only brings in a couple hundred a month.

-SC

How does adjusting app layout to suit a bigger screen cost anywhere near a thousand dollars? Or are you paying a developer to do all the work for you?

----------

Who wants to bet that iOS 9 will be for 64-bit iDevices only?

Dont forget iPad 2 is still supported by ios 8, and iPad 2, 3, and 4 all have 32-bit chips.

I keep wondering when a version of iOS won't include support for none-retina displays, but that hasn't happened.

----------

Good guess. My take is there are so many 32-bit app on the store, I don't see them purging them on the store via iOS 9.

64 bit OSes can run 32 bit apps. 64 bit iOS 7 still runs older apps :)
 
macrumours february 2015

Apple apps updated to 64bit

As of today apples app store is chock full of 64bit apps taking full advantage of the latest hardware.....


first quote with the most up votes

my battery sucks

2nd quote with the most up votes

my battery sucks

here we go again :rolleyes:

3rd quote

safari is snappier

4th quote

safari is snappier

Please you didn't just say that
 
Could someone please clarify for me, does that mean that newer apps aren't going to work on the iPhone 4S and 5?

If the 64-bit architecture is only on the iPhone 5S and later and all apps submitted after February need to be 64-bit, then surely they're no longer going to work on the 4S and 5?

I'm hoping that I'm wrong because it would seem weird to render both of those devices near-obsolete when they both have iOS8 and the 5 still has another year or two of being supported?

The article clearly stated that developers are to build a single binary that supports both. (Last sentence in Apples' email) The older devices will use the 32 bit side. np
 
As a non-developer, I have wondered how much a developer makes from ad supported apps. I paid $2.99 to upgrade from the Sudoko2 to Sudoko2 Pro... Just to remove the ads. I would think that if they offered this option, they must make less than $2.99 from the ads. Either way, seems people are not willing to pay hardly anything for apps any more. Lotta complaining about $5 apps!

Ad support is a joke. You get about 20x as many downloads but only make about 1¢ per download. It's not even close to worth it.
 
Who wants to bet that iOS 9 will be for 64-bit iDevices only?
I think iOS 9 will be the last version to support 32-bit iDevices, as well as, the discontinuation of the A7 and older processors in the next hardware refresh. I am basing this on the fact that Apple is requiring new and updated apps to be compiled with the iOS 8 SDK. This is in preparation for what Apple has planned in the next versions of iOS and OS X.
 
I guess I'm a little confused....It says Apple wont allow developers to submit 32 bit apps...what about all of us iPhone users who dont have a 5S or 6? We have 32 bit phones....correct? Are we being left out in the cold?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.