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.
To continue with Dev Beta or switch to Public Beta?
- Thread starter iBlazed
- Start date
- Sort by reaction score
Going off of 8.3's public beta and Yosemite's public beta, Dev b3 and Public b1 appeared to be the same (in fact, I think they were the same build).
In the previous public betas, the code sent to the PB is almost the same as the code sent to the Developer Preview (DP). The only difference I can remember is that the PB had a Feedback Assistant, and you could log in with the Apple ID on the Public Beta and send feedback. Developers on the DP needed to log into radar.
Since the code is the same, the biggest difference will be the frequency of updates. DPs are updated more frequently than betas. I think there were usually two DPs per beta, but I didn't really check. The advantage of the DP is that you can track more closely what is broken and what gets fixed: you can recheck the bugs you've reported and see if they have been fixed. Or if you need to find a workaround. The advantage of the beta is that stuff is not changing out from under you as often. You don't need to worry about things being broken in a beta as frequently as in a DP. If it's broken, you find a workaround and wait till the next beta, and you don't have to find workarounds as often as the DP, since it isn't released as much.
Since the code is the same, the biggest difference will be the frequency of updates. DPs are updated more frequently than betas. I think there were usually two DPs per beta, but I didn't really check. The advantage of the DP is that you can track more closely what is broken and what gets fixed: you can recheck the bugs you've reported and see if they have been fixed. Or if you need to find a workaround. The advantage of the beta is that stuff is not changing out from under you as often. You don't need to worry about things being broken in a beta as frequently as in a DP. If it's broken, you find a workaround and wait till the next beta, and you don't have to find workarounds as often as the DP, since it isn't released as much.
mikeyteh
macrumors regular
My question with the impending public beta for iOS 9 is this: will developers be allowed to update their apps to the general public that include iOS 9 features? Some apps have been broken by iOS 9 and with the beta being public, I wonder if restrictions will be lifted so devs can "fix" their apps on the App Store
Shirasaki
macrumors P6
I think this is simple.
Developer beta could receive more updates than public beta, such as fast ring and slow ring of windows 10 insider preview.
And feedback provide method is a little bit different, according to what @AlanShutko says. I didn't send any feedback since using El capitan from DP1, by the way.
If you prefer frequent update and tend to keep a closer track of Apple software development, choose DP. If you want to receive beta slower, and send feedback easier, choose PB.
Developer beta could receive more updates than public beta, such as fast ring and slow ring of windows 10 insider preview.
And feedback provide method is a little bit different, according to what @AlanShutko says. I didn't send any feedback since using El capitan from DP1, by the way.
If you prefer frequent update and tend to keep a closer track of Apple software development, choose DP. If you want to receive beta slower, and send feedback easier, choose PB.
Shirasaki
macrumors P6
I have been told that currently App Store does not allow developer use new features in iOS 9 to submit software. But if software issue is not related to iOS 9, I think this would be fine. I am not a developer, though.
lagwagon
Suspended
As far as how Public Beta went for both 8.3 and 8.4 the Developer Preview was not updated more often at all. The only difference in both 8.3 and 8.4 was Devs got it one build sooner. That's all, and once PB1 came out with DP2 both were identical. Just labeled as DP and PB for different programs.