Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Why not release the whole thing correctly at once? Instead of working on the design, I pray that iOS 11 solves most of the idiotic bugs that every iOS release has...

Nevertheless, I am loving iOS10
What do you mean by the whole thing correctly at once? There are always going to be bug fixes, tweaks, improvements, and even new features.
[doublepost=1474496704][/doublepost]
But that's what most of the people wants to be sincere tons of emoticons to send...personally i think the notification system is an improvement over 9 however the battery issues i'm having with ios 10 make it not worth it at least right now.

How much for this beta to become official? 2? 3? weeks? that's a lot of time and i really doubt it will fix the battery issues some of us are having.
You think 10.1 will be finalized and released in just a matter of a few weeks?
 
I have little hope iOS will bring star rating back in stock music app.
However, please allow users to use third party apps to play local music without the need of Apple Music app. I do not need Apple Music in the future.
 
Welcome to BETA. BTW have had no issues with carrier T-Mobile 25.2, 25.1, or 25.0
your correct, this is BETA Software, i figured i would try it out to see how the software worked and to see if there was in fact a carrier update as my service is somewhat spotty, however i haven't seen much of a difference as ive only had my iphone 7 since launch day and things like this don't get worked out until the phone has been out for a month or two
 
Why is this ok that there is an update every week? Stop shipping broken software
Where is there an update every week?

There's no such thing as bug free software when it comes to anything even slightly complex, let alone something like an OS. That's not to mention that there are always tweaks, improvements, and additions as well, which have nothing to do with anything being broken.
 
Why is this ok that there is an update every week? Stop shipping broken software
Where is there an update every week?

There's no such thing as bug free software when it comes to anything even slightly complex, let alone something like an OS. That's not to mention that there are always tweaks, improvements, and additions as well, which have nothing to do with anything being broken.

have you ever coded a simple program? I took programming in high school and its a lot more in debth than you might think! C DM your right, especially with the probably 5 million (Easily) lines of code there must be within IOS.
 
im not sure why they took it away. the worst change they made in ios10.
[doublepost=1474478743][/doublepost]siri has gotten dumber it seems. I can't tell her to "drive home" (get directions to home works however) or "remind me about this email" anymore. hope they fix this.
OH NO! I didn't notice that! I use the email reminder thing for work all the time! That's so annoying. That was my favorite Siri feature as sad as that sounds...
 
Where is there an update every week?

There's no such thing as bug free software when it comes to anything even slightly complex, let alone something like an OS. That's not to mention that there are always tweaks, improvements, and additions as well, which have nothing to do with anything being broken.

Its about quality. When you develop software, you decide what your acceptance criteria is to go live, some organisations have a very high standard, where they will not allow a release to go live if there are x amount of defects of varying levels of severity, others will push out a release no matter what to meet a deadline and follow it up with a patch.

The problem is that software development over the years has adopted the later, release something to meet marketing deadlines, and fix it once live.

I am not happy about this, both as a customer and someone who has been in software development for nearly 20 years. Software quality has dropped, largely facilitated by the fact that we can now push updates so easily, means the initial release can be of such a lower standard, as we can fix it....soon after.

So this brings us onto apple, they have brought this onto themselves, a large release every 12 months to meet marketing is not realistic from a SDLC, quality will fall as you chase feature development, and hence we get bugs.

The idea though that we should be of the mindset that bugs are fine, no....... I strongly disagree with you, as a customer we should be getting the best possible product that is not faulty. Your mindset sounds like that of a developer, even such, you should not be accepting bugs as a forgone conclusion of development, only time that becomes in anyway acceptable is when the dev team is being pushed to get features out at the cost of QA, and hence creation of tech debt, and business accepts the consequences.

So the short of it, Apple can improve QA of their software, to do so, it needs to stop marketing dictating the development life cycle, until such time we will continue to get software that is buggy, and more releases to correct these bugs, buggy software is not acceptable though, nor is the concept that cause we work in software development, bugs are okay are a way of life in our industry. Fact of the matter is, we build many systems, critical systems that are bug free by the time they go life, though that takes Time and Money.

Whiile you are correct, there is not such thing as bug free software, cause you cannot test to infinity......there is definitely software shipped that does not have level 1 critical bugs, and these days more and more software is shipped with level 1 critical bugs....which are corrected soon after launch, and that is not good enough. The user should not just accept this.
 
Its about quality. When you develop software, you decide what your acceptance criteria is to go live, some organisations have a very high standard, where they will not allow a release to go live if there are x amount of defects of varying levels of severity, others will push out a release no matter what to meet a deadline and follow it up with a patch.

The problem is that software development over the years has adopted the later, release something to meet marketing deadlines, and fix it once live.

I am not happy about this, both as a customer and someone who has been in software development for nearly 20 years. Software quality has dropped, largely facilitated by the fact that we can now push updates so easily, means the initial release can be of such a lower standard, as we can fix it....soon after.

So this brings us onto apple, they have brought this onto themselves, a large release every 12 months to meet marketing is not realistic from a SDLC, quality will fall as you chase feature development, and hence we get bugs.

The idea though that we should be of the mindset that bugs are fine, no....... I strongly disagree with you, as a customer we should be getting the best possible product that is not faulty. Your mindset sounds like that of a developer, even such, you should not be accepting bugs as a forgone conclusion of development, only time that becomes in anyway acceptable is when the dev team is being pushed to get features out at the cost of QA, and hence creation of tech debt, and business accepts the consequences.

So the short of it, Apple can improve QA of their software, to do so, it needs to stop marketing dictating the development life cycle, until such time we will continue to get software that is buggy, and more releases to correct these bugs, buggy software is not acceptable though, nor is the concept that cause we work in software development, bugs are okay are a way of life in our industry. Fact of the matter is, we build many systems, critical systems that are bug free by the time they go life, though that takes Time and Money.

Whiile you are correct, there is not such thing as bug free software, cause you cannot test to infinity......there is definitely software shipped that does not have level 1 critical bugs, and these days more and more software is shipped with level 1 critical bugs....which are corrected soon after launch, and that is not good enough. The user should not just accept this.
But in the context of the post that I replied to, it doesn't really seem to have much to do with a first beta for an upcoming 10.1 release being released today.
 
Yeah, I know, I was just annoying quoting everyone. But I wanted to get this wrapped up into one place so everyone is on the same page.

First off, the behavior in the URL/Search field is likely purposeful, since the idea COULD BE that you're typing in an IP address. That it sticks to numbers EVEN IF you use some other form of punctuation like a dash or comma or a semicolon should probably be reported as bug in and of itself (since only numbers, periods, and maybe colons are allowed in IP addressing). I tested, and this behavior is the same as far back as iOS 9.3.3.

However, SECOND, the observed behavior in OTHER text fields as of iOS 10b7 does NOT occur on 9.3.3 (I'm assuming, since Mlrollin91 specified iOS10b7, it WAS observed there first). It would seem that perhaps Apple is re-using the same Keyboard switching logic/code from the URL/Search field in all text fields, which would be, IMHO and apparently others', WRONG.

So, for the record, wrong behavior albeit likely "works as intended" in the URL/Search field that has been going on for a while, wrong/weird/annoying behavior in all text fields in Safari since iOS10b7. Two bugs. Might want to update Apple in that fashion, make sure they understand where you're seeing it (they sometimes can be aggravatingly dense on such things). [I don't have iOS 10 installed on anything to test, but I keep notes on Known Issues because I have clients. Who complain. So I greatly appreciate the reporting and the detail. ;)]

Most people aren't typing IP addresses or even know what an IP address is. Those of us who have a need to type an IP into the address field are a small minority and even though I sometimes have a need to, it's very, very rare.
 
What do you mean by the whole thing correctly at once? There are always going to be bug fixes, tweaks, improvements, and even new features.
[doublepost=1474496704][/doublepost]
You think 10.1 will be finalized and released in just a matter of a few weeks?

I don't know man the beta was released for testing just today so i expect it will be released in perhaps 2 weeks? i guess? 1 month will be too much Apple is not that slow...

BTW:

Well i just finish downgrading, i'm back to ios 9.3.5 and i had 0 issues so far my battery life is back, to be sincere ios 9.3.5 was flawless imo but ios 10.0.1 was not for me.

I don't regret having installed ios 10, i didnt want to do it at the beggining to be sincere i was afraid of exactly this battery drain but i read reviews saying one had to taste it, and i took that risk and guess what? it happened battery issues...sigh.

IMO the new OS is not ready yet at least for the iphone 6s model.

I'm not "happy" of having to perform this downgrade (first time i did it with an Apple phone) but everything went fine, the process was pretty simple.

Obviusly in the future when new ios 10 firmwares are released and one of them fix this battery issue i'm gonna install ios 10 again, one can't get stuck in the past but right now no thanks fix your game Apple!
 
I don't know man the beta was released for testing just today so i expect it will be released in perhaps 2 weeks? i guess? 1 month will be too much Apple is not that slow...

BTW:

Well i just finish downgrading, i'm back to ios 9.3.5 and i had 0 issues so far my battery life is back, to be sincere ios 9.3.5 was flawless imo but ios 10.0.1 was not for me.

I don't regret having installed ios 10, i didnt want to do it at the beggining to be sincere i was afraid of exactly this battery drain but i read reviews saying one had to taste it, and i took that risk and guess what? it happened battery issues...sigh.

IMO the new OS is not ready yet at least for the iphone 6s model.

I'm not "happy" of having to perform this downgrade (first time i did it with an Apple phone) but everything went fine, the process was pretty simple.

Obviusly in the future when new ios 10 firmwares are released and one of them fix this battery issue i'm gonna install ios 10 again, one can't get stuck in the past but right now no thanks fix your game Apple!
How long has it taken to release various x.y releases in the past from the point the first beta came out? Certainly more than a couple of weeks. Now that's not to say something different couldn't happen, but then again it doesn't really seem like there's much to really indicate that it would.
 
How long has it taken to release various x.y releases in the past from the point the first beta came out? Certainly more than a couple of weeks. Now that's not to say something different couldn't happen, but then again it doesn't really seem like there's much to really indicate that it would.

Ah i can't answer that with exactitude to be sincere but i don't know i don't remember an entire month happened perhaps i'm totally wrong but i know a site that may help with the dates let me google it.

Found it:

https://ipsw.me/history

ios 9.0 was released:
Wednesday, September 16, 2015

ios 9.0.1:
Wednesday, September 23, 2015

Just a few days passed...

Now for ios 9.1:
Wednesday, October 21, 2015

more than an entire month passed...

To be fair i don't know what is Apple's next step i suppose next update is gonna be 10.1 not 10.0.2 and beta was released today so perhaps 3 weeks?

In the meantime i just went back to ios 9.3.5 sucessfully! FGS...at least on the iphone 6s, i update to ios 10 the ipad air 2 and the ipod touch 6 but i'm gonna leave those with ios 10.
 
Last edited:
Ah i can't answer that with exactitude to be sincere but i don't know i don't remember an entire month happened perhaps i'm totally wrong but i know a site that may help with the dates let me google it.

Found it:

https://ipsw.me/history

ios 9.0 was released:
Wednesday, September 16, 2015

ios 9.0.1:
Wednesday, September 23, 2015

Just a few days passed...

Now for ios 9.1:
Wednesday, October 21, 2015

more than an entire month passed...

To be fair i don't know what is Apple's next step i suppose next update is gonna be 10.1 not 10.0.2 and beta was released today so perhaps 3 weeks?

In the meantime i just went back to ios 9.3.5 sucessfully! FGS.
Right, for an x.y minor release (as opposed to an x.y.z bug fix release) it's usually something more than a couple of weeks.
 
Right, for an x.y minor release (as opposed to an x.y.z bug fix release) it's usually something more than a couple of weeks.

Ok but do you think they are gonna go this time x.y and totally skipping any x.y.z? that would be pretty lame. I mean thinking on those battery drains happenings for example, i guess only Apple knows...
 
Ok but do you think they are gonna go this time x.y and totally skipping any x.y.z? that would be pretty lame. I mean thinking on those battery drains happenings for example, i guess only Apple knows...
Hard to really say. It's likely they will release something like 10.0.2 before they get 10.1 out, but it's possible that it might not happen like that.
 
But in the context of the post that I replied to, it doesn't really seem to have much to do with a first beta for an upcoming 10.1 release being released today.

There is actually. Using 10.1 as an example, its the first release that will include functionality and lower bug fixes that were not completed for 10.0 , it's all related and forms the product backlog.

If apple along the way runs into critical bugs/broken functionality that cannot wait till 10.1 they will plan a 10.0.1 etc (which I think is out already, yup first patch already issued).

The more 10.0.x releases you see .....the worse is the quality of 10.0

The issue people are seeing , is that in recent years, we are getting a number of 0.0.x releases straight after going live, which indicates not bugs, but critical bugs that must be fixed asap. These are not acceptable, especially if the trend continues. It also means that software is being rushed out to meet deadlines.....

Bug fixes for 10.1 are fine and part of software development lifecycle , these are bugs that provide acceptable level of service, these are the ones people generally accept as "going" to be fixed.

From experience as feedback is flowing back in, release 10.0.2 is already in the works.
 
Welcome to BETA. BTW have had no issues with carrier T-Mobile 25.2, 25.1, or 25.0


I've been using the beta since June. I was responding to a question someone else asked, if the new update today fixed the T-Mobile issue. You are lucky if you didn't have any issues, some of us has had problems since T-Mobile released the Carrier update which was released the day iOS 10 GM was released not during the betas.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.