Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
2 more new things I noticed,

1. New zoom animation on wallpaper when waking the phone from sleep.

2. New fade out animation when press a number on the dial pad.
 
Actually, it is probably being force-closed by iOS due to low memory (check the logs), which isn't really the same as crashing due to iOS bugs (i.e., it is intentional behavior). It is likely designed to deter a single [badly coded/overly complex/poorly optimized] web page (or app, really) from trying to use more RAM than the phone has. The idea is "why would you want to keep something loaded that is barely usable in the first place?"

But you are right, browser crashes are not okay.

Disclaimer: I'm inferring much of this and simplifying somewhat.


Let me, as a programmer who played with RAM allocation back in even the iPhone 3G times when every single byte counted, chime in.

There is absolutely no memory protection in iOS. This means if you allocate a given size of RAM, and there is not so much free RAM available, your app will crash. This is why many apps crash now and then when run without manually killing all previous apps / resetting first.

This is REALLY a PITA as

- malloc()'s simply failing (signalling it didn't allocate the asked-for RAM) would be preferred to (the current) crashing for obvious results (much better for end users; you can gracefully exit or, say, opt for displaying "Not enough RAM, kill bg tasks / reset" messages.)

- UIWebView behaves exactly the same way: if you load a page that simply doesn't fit in the memory when decoded, your app will crash. And, as I've pointed out above, UIWebView uses TONS of memory - sometimes even hundreds of megabytes for a larger Web page on a Retina iPad.

----------

Because it is CRAP website... ;)

Not necessarily. I'll measure its RAM usage and report back. (After sleeping first, I think - it's very late in here.)
 
Sometimes your data gets screwed up, sometimes you hit a page that is implemented so poorly that your browser crashes. You can't expect software to be able to handle every single edge case and random error.

Yes you can. Content should never be able to crash the browser. If the content is malformed it will display incorrectly, but the browser should always be able to display a representation of the content.

Since HTML and CSS do not execute (and JavaScript executes inside of a sandbox), the browser crashing in response to bad web content indicates a severe failure to protect against untrusted data. And yes, all content from the web is to be untrusted, even expected to be malicious, when you're writing a browser.

If you can find a piece of HTML/CSS/JavaScript that reproducibly crashes Safari, or any browser, please report it to the appropriate parties. It's a very severe security risk.
 
It's great to see Apple addressing complaints instead of going down their own arrogant path.

List view under Calendar dates is extremely welcome. I'm also pleased to see the return of buttons (buttons don't affect me much, but it adds intuitiveness for new users). I still have issue with some of the functionality (Contacts layout and the lack of at-a-glance info in Notifcation Centre), as well as the excessive amount of white, but this is a step in the right direction.

I'm looking forward to iOS 7.2. If they keep going in this direction then I may stay with iPhone.
 
Decided to avoid B1, but couldn't resist trying out B2...
On the 5S smoother but not drastic, on the Air a much bigger difference!
Specially the multifinger gestures, and overall a good step in the right direction.
:apple:
 
I've done a LOT of work with UIWebView - the core component of Safari. I've talked a lot with the dev of iCab Mobile, Alexander Clauss, on these matters. So I do know what I'm speaking about:

It's mostly because of the enormous RAM memory usage of that widget that crashes (and, in Safari, killed tabs) are abound, not those of Web pages. Surely, some Web pages can crash Safari even with plenty of RAM available (this is how the 4.3 JB became possible), but you need to search very hard to find such pages. Casual pages don't crash Safari.

Web pages or apps (or rather with apps), I acknowledged them both as contributing.

Let me, as a programmer who played with RAM allocation back in even the iPhone 3G times when every single byte counted, chime in.

There is absolutely no memory protection in iOS. This means if you allocate a given size of RAM, and there is not so much free RAM available, your app will crash. This is why many apps crash now and then when run without manually killing all previous apps / resetting first.

This is REALLY a PITA as

- malloc()'s simply failing (signalling it didn't allocate the asked-for RAM) would be preferred to (the current) crashing for obvious results (much better for end users; you can gracefully exit or, say, opt for displaying "Not enough RAM, kill bg tasks / reset" messages.)

- UIWebView behaves exactly the same way: if you load a page that simply doesn't fit in the memory when decoded, your app will crash. And, as I've pointed out above, UIWebView uses TONS of memory - sometimes even hundreds of megabytes for a larger Web page on a Retina iPad.


Really the biggest problem I've seen is from multitasking between two programs that are fighting to the death for RAM (iBooks with a large pdf and Safari, for instance). Honestly, I feel the worst for you guys (developers). It must be painful to have to read through all those 1-star reviews that aren't reviewing the actual content of the app but are complaining about "crashes" that are more than likely just LowMemory errors. I'd imagine dropping 3GS (and earlier) support must substantially reduce the amount of these non-reviews.

RAM memory

That made me lol out loud :D
 
Well excuse me Mr. I Am A Developer - some of us would like our phones to be actually functioning properly without bugs and crashes left and right.

The only reason I want to upgrade is due to the fact that iOS 7.0.3 and 7.0.4 have been complete ***** for me in regards to usability.

Phone calls do not come in and the only way I know I had a phone call is because a few minutes later I get a VM indicating so.

On top of that iOS 7 is so buggy that I have to constantly press my home button before it actually even does anything. No my home button isn't defective nor is it broken, it worked fine all day every day while I was on iOS 6.

Odd. I'm running iOS 7 on 3 devices (iPhone and 2 iPads) and do not have any usability on 7.0.3 or 7.0.4. Perhaps you should make a genius bar appointment.
 
The new Control Centre animation makes me think as if it was made of jelly :3
 
How original. You're like an Apple devoted version of Carlos Mencia.

I'm not the one being original, I'm just stealing your act.

In all seriousness, why is it a problem for you if someone gives a positive anecdote about iOS 7? I understand this site is the place where people come to complain about all things Apple, but it's not a sin to like Apple products and software...
 
Not sure if you were sarcastic, but Apple usually doesn't put anything related to user facing features in beta release notes unless it can affect developers.

This is also true for bug fixes in the user interface or built-in apps, some fixes might not be listed in the release notes.

It was sarcasm. ;)
 
Yes! Love that! Same on the lock screen?

Yep same on lock screen :)

----------

Just to be clear. You can tap the are where the song and album title are now and it'll take you to the music app as well. This isn't new in 7.1.

(Though who would know given that text and buttons look the same now...)

Know what you mean, what I'm saying is that now you can launch the music app even when no music is playing (music.app is completely closed) rather than first having to launch the music app, start a song and then have the ability to go "back" into the music app via control centre.

Hope that makes sense haha because my explanation seems really bad when I read it back to myself :)
 
It's a shame dark keyboard is gone. But maybe it means they are working on a system-wide dark look? Or they could move it from Accessibility to the Keyboard Settings?
 
Have to say that every time i read this updates I simply laugh...
This are the big changes?
Changing yahoo icon?
Are you kidding me apple?
What is going on there, the base at cupriteno are simply disconnected from the tech market.
This year unless apple will introduce something very diffrent in ios 8, it is the end of this os.
And the final winning of the android.
 
Have to say that every time i read this updates I simply laugh...
This are the big changes?
Changing yahoo icon?
Are you kidding me apple?
What is going on there, the base at cupriteno are simply disconnected from the tech market.
This year unless apple will introduce something very diffrent in ios 8, it is the end of this os.
And the final winning of the android.
Might be good to actually read the available information and see that there are quite a few more changes beyond some little things like Yahoo! logo changes (they they probably just had to do and call out contractually).
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.