This is ridiculous!!!! WHY? [MS Office requires iOS 7]

[roadbloc]

That's definitely lazyness on the devs' part, unless they really use some non-existing stuff. I generally only use iOS7-only stuff in conditional blocks and try to come up with something similar / workaround in the code targeted at earlier OS'es..

It could be. But it could be Microsoft simply catering for Apple's support lifecycle. In Apple land only the newest software version is supported, stick to one version for a couple of years and you'll find yourself out of support and running out of usable Apps.

In Microsoft land however, software is supported for a much longer time. Hence why iTunes for Windows is still made to work on XP. And yet the very same iTunes requires Snow Leopard (an OS released a whole 8 years after XP) because Apple have a different support lifecycle for their software.

 

[rhett7660]

I know when I updated to iOS 7.1 on my third gen iPad, it was stuttering during the transitions. I had to turn on the animations. Only then did the stuttering if you will stop and it was smooth again. It was very jerky after the update.

I had those animations turned off after the upgrade to 7.0. They was a difference once I turned them back on.

 

[grandM]

just use pages, numbers etc...

 

[themumu]

As an iOS developer, I can totally understand and agree with their reasons for sticking to iOS 7 only. You wouldn't believe how much of a hassle it can be to support old OS versions for complex applications. In a few months they will have to start testing and fixing these apps for another OS release, and will likely support both 7 and 8 for a while. While I don't know exactly what made them decide not to support iOS 6, I suspect it was the fact that supporting it would mean:

• longer development time to ensure iOS7-only features degrade gracefully on 6
• longer testing time for more hardware and OS combinations
• higher likelihood for bugs to appear
• reduced feature set to fit within the same deadlines

Plus, I really love it when a major app drops legacy OS support, because it means even more users will upgrade to latest OS, which makes my decisions to drop iOS 6 even better justified.

Thank you, Microsoft! (Who knew I'd ever say something like that with zero sarcasm.)

 

[\-V-/]

There is no sense in complaining about something that's not going to change. Microsoft isn't ever going to support iOS 6, so either upgrade to iOS 7 or just deal with it. Complaining isn't going to do anything but stress you out. This is reality.

 

[TWO2SEVEN]

You could try this:

http://www.cultofmac.com/272515/youve-got-skills-can-now-dual-boot-ios-7-ios-6-ios-5/

 

[Menel]

I went to download the new office apps for my iPad 3 today, but apparently I can't. I have been looking forward to these why a while now. But I can't because I choose not to download iOS 7 on my iPad 3. I prefer a smooth fluid textured operating system. Anyone else in my shoes here?

Image

You wouldn't like it anyway.

It's got a modern UI, vs the archaic textured UI you prefer.

 

[Menneisyys2]

It could be. But it could be Microsoft simply catering for Apple's support lifecycle. In Apple land only the newest software version is supported, stick to one version for a couple of years and you'll find yourself out of support and running out of usable Apps.

I hope MS does make an attempt at supporting as old OS versions as possible. A lot of people are still using 5.1.1 iPad 1's; for example, in my family, where I've handed down my old iPad 1.

 

[maflynn]

I hope MS does make an attempt at supporting as old OS versions as possible. A lot of people are still using 5.1.1 iPad 1's; for example, in my family, where I've handed down my old iPad 1.

Never going to happen, if there was a glimmer of hope for iOS6, there is absolutely noting for iOS5. There's just too many changes to the APIs to support such a request, especially given the majority of users are on iOS7, i.e., 80% adoption rate.

Source

 

[roadbloc]

I hope MS does make an attempt at supporting as old OS versions as possible. A lot of people are still using 5.1.1 iPad 1's; for example, in my family, where I've handed down my old iPad 1.

As long as Apple continues its current fast support lifecycle for their software, you probably have more chance of waking up on the moon tomorrow morning.

 

[Menneisyys2]

As long as Apple continues its current fast support lifecycle for their software, you probably have more chance of waking up on the moon tomorrow morning.

Again: I'm speaking as a dev that supports every OS versions and architectures (except for natively supporting the 64-bit A7 on the binary level - very few apps do that because of the sometimes huge effort to make the source 64-bit compatible) starting with 4.0.

Depending on the API's you use, it might be comparatively easy to add support for previous iOS versions. At least I don't mind the additional effort. I'd say it takes me only about 10% of my full dev time to properly test and, when needed, adjust the code to run on all previous OS versions, incl. even iOS4.2.1 armv6 devices (the iPhone 3G and iPt2G).

Nevertheless, if the Office suite uses iOS7+ API's (I don't know whether this is the case), adding compatibility for earlier iOS versions may indeed take too much time, if at all possible. There indeed are a lot of new API features in all major iOS version jumps that are very hard to properly implement in earlier OS versions (see for example my previous note on NSMutableAttributedString's addAttribute:value:range, which I didn't really bother implementing for devices running under pre-iOS6 for displaying arbitrary, compile-time-unknown HTML markup). Dunno.

 

[dimzen]

Tried the web version of Office?
https://office.live.com

I only have iOS7, so don't know how it runs on iOS6 :/

 

[roadbloc]

Again: I'm speaking as a dev that supports every OS versions and architectures (except for natively supporting the 64-bit A7 on the binary level - very few apps do that because of the sometimes huge effort to make the source 64-bit compatible) starting with 4.0.

Depending on the API's you use, it might be comparatively easy to add support for previous iOS versions. At least I don't mind the additional effort. I'd say it takes me only about 10% of my full dev time to properly test and, when needed, adjust the code to run on all previous OS versions, incl. even iOS4.2.1 armv6 devices (the iPhone 3G and iPt2G).

Nevertheless, if the Office suite uses iOS7+ API's (I don't know whether this is the case), adding compatibility for earlier iOS versions may indeed take too much time, if at all possible. There indeed are a lot of new API features in all major iOS version jumps that are very hard to properly implement in earlier OS versions (see for example my previous note on NSMutableAttributedString's addAttribute:value:range, which I didn't really bother implementing for devices running under pre-iOS6 for displaying arbitrary, compile-time-unknown HTML markup). Dunno.

As I said, developers (except you it seems) will only support the iOS versions they have to... the ones Apple support. No support, no new apps. Only Apple can change this.

 

[maflynn]

Again: I'm speaking as a dev that supports every OS versions and architectures (except for natively supporting the 64-bit A7 on the binary level - very few apps do that because of the sometimes huge effort to make the source 64-bit compatible) starting with 4.0.

Your the exception not the rule. Plus we have no idea of the features that Office has requires specific APIs that are only present in iOS7.

Its a moot point, since Office came out requiring iOS7. it is what it is, and the the chances of them releasing an update making it compatible for older versions of iOS are nil especially when iOS8 is coming around the corner.

----------

Depending on the API's you use, it might be comparatively easy to add support for previous iOS versions. At least I don't mind the additional effort. I'd say it takes me only about 10% of my full dev time to properly test and, when needed, adjust the code to run on all previous OS versions, incl. even iOS4.2.1 armv6 devices (the iPhone 3G and iPt2G).

but why do all that work and support when the majority of iOS users are on iOS 7 as it is. Time is money, and why spend that time for diminishing returns, and possible increase in bugs/support issues.

 

[Menneisyys2]

but why do all that work and support when the majority of iOS users are on iOS 7 as it is. Time is money, and why spend that time for diminishing returns, and possible increase in bugs/support issues.

1. I have most iDevice models ever released and very often hand them out to my customers so that they can test my apps on them too. I prefer not to leave any of my devices unable to be handed out

2. it's a definite business / competitive advantage in the AppStore to be the only app in its category to have not only 4.3+, but even 4.0-4.2.1 + armv6 support. Anyone looking for an app in the category on his/her iPhone 3G will only be able to install mine and not those of the competition. I think this is worth the additional effort of separately compiling (for distribution) my apps under Xcode 4.4 for armv6 and manually adding the resulting armv6 binary to the iOS4.3+/armv7/armv7s fat binary produced by Xcode 5.1.

----------

As I said, developers (except you it seems) will only support the iOS versions they have to... the ones Apple support. No support, no new apps. Only Apple can change this.

Well,it's their decision. I do consider supporting even iPhone 3G's / iPt2G's even in my latest apps a definitive competitive advantage. And it assumes very little additional effort:

- save all XIB's as 4.6-compatible
- not using iOS5+ features like storyboards or ARC (that's not a problem for me as, my apps having been developed since the iPhone OS 3 days, they're all manually memory-micromanaged and non-Storyboard-based)
- using runtime conditional blocks for iOS6/7-only features (like the above [NSMutableAttributedString addAttribute:value:range])
- when needed, adding some kind of device model-specific code not to start memory-hungry operations like loading Foursquare images along with the venue names

All this is pretty simple, unless you absolutely need to implement some kind of missing functionality in earlier OS versions. With the above-mentioned [NSMutableAttributedString addAttribute:value:range] for example, which is damn hard to implement in pre-iOS6 for random HTML input, I've chosen not to bother with trying to parse the markup. That is, I just output unformatted (no bold, no italic etc.) text under iOS4/5.

 

[zorinlynx]

I would feel bad for you if you had an iPad 1 that can't run iOS 7. But you're staying in the past by choice, and staying in the past means you'll be running software from the past, too.

It's like running Windows 95 on a PC and whining because I can't play Team Fortress 2.

Just move on, trust me, it'll be less painful in the long run.

 

[Han Solo 1]

Griping about performance means you haven't actually used it.

Well I have, and he's right. iOS 7 sucks. Milky white garbage everywhere. Can't text at night without burning my eyes.

I hate iOS 7.

Don't upgrade, OP.

 

[jrswizzle]

Well I have, and he's right. iOS 7 sucks. Milky white garbage everywhere. Can't text at night without burning my eyes.



I hate iOS 7.



Don't upgrade, OP.

Your opinion....that's fine if you choose not to. But it's not Apple's fault when apps keep up with advancing OSes and you're stuck in the past.

 

[irnchriz]

I went to download the new office apps for my iPad 3 today, but apparently I can't. I have been looking forward to these why a while now. But I can't because I choose not to download iOS 7 on my iPad 3. I prefer a smooth fluid textured operating system. Anyone else in my shoes here?

Image

Unlucky. 7.1 runs fine on my wife's iPad 3rd gen, so does Word and Excel.

 

[iMcLovin]

I thought the new look of iOS was a bold change from apple. Now seeing the look of iOS 6 it feels like warping back in time to the 90's. Way too shaded and glossy. Icons almost look dirty because of all the gradients and bevels... Really horrible and old fashioned. I'm so glad apple don't stop evolving and get stuck in time just because some users are! Days of bevels and textured gloss are over, get used to it. It's pointless to refuse and eventually you will need to adapt anyway. Ios7 is a fresh breath vs. the fogged and cloudy and inconsistent design I iOS 6....end of discussion I can't wait for osx to get some of the cleaner look too.

 

[deluxeshredder]

I thought the new look of iOS was a bold change from apple. Now seeing the look of iOS 6 it feels like warping back in time to the 90's.

90s UI design was far more like iOS 7 than iOS 6.

Way too shaded and glossy.

And way too readable fonts and no yummy yellow on white.

Icons almost look dirty because of all the gradients and bevels... Really horrible and old fashioned.

iOS 7's icons have much more prominent gradients.

I'm so glad apple don't stop evolving and get stuck in time just because some users are! Days of bevels and textured gloss are over, get used to it.

Years of good mainstream music are over, but I have no problem finding good indie music. Or avoiding fast food and iOS 7.

It's pointless to refuse and eventually you will need to adapt anyway. Ios7 is a fresh breathvs. the fogged and cloudy and inconsistent design I iOS 6

iOS 7 was not a fresh breath for me, I have been enjoying flat design on Andoid for about a year before.

....end of discussion I can't wait for osx to get some of the cleaner look too.

Chances you'll get it.

 

[iMcLovin]

90s UI design was far more like iOS 7 than iOS 6.





And way too readable fonts and no yummy yellow on white.





iOS 7's icons have much more prominent gradients.





Years of good mainstream music are over, but I have no problem finding good indie music. Or avoiding fast food and iOS 7.





iOS 7 was not a fresh breath for me, I have been enjoying flat design on Andoid for about a year.





Chances you'll get it.

Well if you think ios7 looks more 90s because of lack of gradients and metallic shading then it's impossible to have a discussion. Then you obviously don't see the. Evolvement of design over the years.

ios7 may have more prominent gradients but they haven't got textured gradients with beveled edges and a layer of glass reflection on top...which is getting out of date and is used fairly decent in osx but over the top in ios6

 

[TheWheelMan]

I have an iPad 3 with IOS 7.1 (with a brand new iPad Air to be delivered tomorrow, YAY!), and it runs fine. I think it's laughable that people want Microsoft to potentially cripple their software by backwards compatibility, because they would then be mad because of the features that might be lacking BECAUSE of the sacrifices that might have been made for backwards compatibility.

 

[Menneisyys2]

I have an iPad 3 with IOS 7.1 (with a brand new iPad Air to be delivered tomorrow, YAY!), and it runs fine. I think it's laughable that people want Microsoft to potentially cripple their software by backwards compatibility, because they would then be mad because of the features that might be lacking BECAUSE of the sacrifices that might have been made for backwards compatibility.

Again:

- it's not known exactly what iOS7+-only features they use and the effects of not using them under earlier OS'es. Again: see my earlier example of formatting HTML text in my own AppStore apps. I just ignore bold / italic tags in HTML markup when presenting it under iOS versions prior to iOS6. Is it that big a problem for end users? I don't think so - it's a decent sacrifice, IMHO, given that I can give my users a runnable, working version and not-that-dumbed-down experience, instead of telling them to upgrade their iOS version or get a newer iDevice. Let's not forget that many of us prefer old OS versions for, say, full jailbroken windowed multitasking support (see the iOS5-only Quasar).

- method calling in Objective-C is superior to, say, Java in that you can deliver a binary compiled against the latest iOS SDK with conditional execution. You don't need to manually use purely dynamic calls, which are very-very awkward under Java (see reflection). (An example of using reflection) Just not allowing the system to execute some kind of code if certain runtime conditions aren't met is very-very easy under iOS.

 

[shandyman]

1. I have most iDevice models ever released and very often hand them out to my customers so that they can test my apps on them too. I prefer not to leave any of my devices unable to be handed out

2. it's a definite business / competitive advantage in the AppStore to be the only app in its category to have not only 4.3+, but even 4.0-4.2.1 + armv6 support. Anyone looking for an app in the category on his/her iPhone 3G will only be able to install mine and not those of the competition. I think this is worth the additional effort of separately compiling (for distribution) my apps under Xcode 4.4 for armv6 and manually adding the resulting armv6 binary to the iOS4.3+/armv7/armv7s fat binary produced by Xcode 5.1.

----------



Well,it's their decision. I do consider supporting even iPhone 3G's / iPt2G's even in my latest apps a definitive competitive advantage. And it assumes very little additional effort:

- save all XIB's as 4.6-compatible
- not using iOS5+ features like storyboards or ARC (that's not a problem for me as, my apps having been developed since the iPhone OS 3 days, they're all manually memory-micromanaged and non-Storyboard-based)
- using runtime conditional blocks for iOS6/7-only features (like the above [NSMutableAttributedString addAttribute:value:range])
- when needed, adding some kind of device model-specific code not to start memory-hungry operations like loading Foursquare images along with the venue names

All this is pretty simple, unless you absolutely need to implement some kind of missing functionality in earlier OS versions. With the above-mentioned [NSMutableAttributedString addAttribute:value:range] for example, which is damn hard to implement in pre-iOS6 for random HTML input, I've chosen not to bother with trying to parse the markup. That is, I just output unformatted (no bold, no italic etc.) text under iOS4/5.

So you waste time adding support for iOS versions that are less than 3% of the user base by going back to iOS 4 & 5?! what a waste of time and effort...

http://cdn.macrumors.com/article-new/2014/03/ios7adoptionrate_march.png