Not sure if this has been asked cant seem to find anything. Which one is better the Developer beta 2 or the public beta that just came out or is it the same as developer beta 2? Thanks!
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Developer beta or public beta
- Thread starter xxjrsmith3xx
- Start date
- Sort by reaction score
Developer beta is received earlier than public beta. Nothing much different other than that one.
You don't need to care too much about it actually.
You don't need to care too much about it actually.
The developer beta and public beta are typically the same build when released together like dev b2 and public b1, the most notable difference (other than target audience) is the dev betas are updated more often than the public betas and may have device breaking bugs that typically only developers/strong computer users know how to work around.
If you want a stable pre-release stick with the public beta, if you want newer builds faster (even though they may be worse in stability) go with the developer beta.
Public betas are designed for users to test out the software and provide feedback on bugs they have encountered.
The developer betas are designed with the most recent preview release of Swift and is provided to developers to test out the software for bugs as well as prepare their applications to run on the next operating system version so fewer bugs are encountered and make the transition to iOS 10/macOS Sierra as painless as possible for users.
My suggestion is to stick with the release cycle that pertains most to you.
If you want a stable pre-release stick with the public beta, if you want newer builds faster (even though they may be worse in stability) go with the developer beta.
Public betas are designed for users to test out the software and provide feedback on bugs they have encountered.
The developer betas are designed with the most recent preview release of Swift and is provided to developers to test out the software for bugs as well as prepare their applications to run on the next operating system version so fewer bugs are encountered and make the transition to iOS 10/macOS Sierra as painless as possible for users.
My suggestion is to stick with the release cycle that pertains most to you.
Since they are the same or almost the same build, if you're not a developer then it may be best to stick with the public beta. Should you have to take it in for service(related or unrelated to the beta) you won't have any tricky questions about being a dev or not to answer.
Im sorry but that's just wrong. Developer betas do not update more often. The ONLY difference is the developers get 1-2 builds before the public beta starts. Typically it's 2, but in the case here of iOS 10 it's only 1. From
Now on till iOS 10.0 gets officially released they both will receive builds the same week. With the developer getting it a day or two before the public beta. Not more often.
And they are identical builds when released. There is no "design" difference between the two beta builds.
Not sure where you got your info from.
I did mention that the respective pb build that comes out with the developer beta is the same build, so if anything I might be partially wrong, the fact is developer betas tend to have more releases than the public beta builds.
Also I was going off of memory, didn't think I'd actually have to make a point. Since someone is asking about whether to use public or developer betas, they are obviously not a developer and should be using the public beta, I think that's more important than scrutinizing the details about releases of builds.
Both currently include the feedback app.
[doublepost=1468015770][/doublepost]
I was simply just clearing up misinformation. Pretty important when giving someone who may not know a lot on the subject that they get correct info.
Edit -
https://developer.apple.com/support/beta-software/
If you encounter any problems with beta software or if you would like to request enhancements to frameworks or API, please submit a report through Apple Bug Reporter.
https://beta.apple.com/sp/betaprogram/
As a member of the Apple Beta Software Program, you’ll be able to enroll your Mac or iOS device to access the macOS and iOS public betas. Each public beta comes with a built-in Feedback Assistant app
How do I provide my feedback to Apple?
The macOS and iOS public betas come with the built-in Feedback Assistant app, which can be opened from the second page of the Home screen on your iOS device or from the Dock on your Mac. The Feedback Assistant app is also available from the help menu of any app by choosing 'Send Feedback’. If you experience an issue or something does not work as expected, send your feedback directly to Apple with Feedback Assistant.
My apologies - i'd not seen this, and having read the beta program info and the developer one, it seemed beta got the Feedback Assistant, Developerbuild got bug reporter. My bad!
https://developer.apple.com/support/beta-software/
If you encounter any problems with beta software or if you would like to request enhancements to frameworks or API, please submit a report through Apple Bug Reporter.
https://beta.apple.com/sp/betaprogram/
As a member of the Apple Beta Software Program, you’ll be able to enroll your Mac or iOS device to access the macOS and iOS public betas. Each public beta comes with a built-in Feedback Assistant app
How do I provide my feedback to Apple?
The macOS and iOS public betas come with the built-in Feedback Assistant app, which can be opened from the second page of the Home screen on your iOS device or from the Dock on your Mac. The Feedback Assistant app is also available from the help menu of any app by choosing 'Send Feedback’. If you experience an issue or something does not work as expected, send your feedback directly to Apple with Feedback Assistant.
Last edited:
Honestly I would recommend on waiting until Public Beta release 2.
There will be a lot of users signing up for public beta compared to developer beta so a lot of bugs that are existing now will probably be reported and "may" be fixed by the next public beta 2 release (which may come out in maybe 3 weeks or so).