If you’ve ever wanted to take an early look at new versions of Apple’s operating systems before they launch, and maybe help shape them in the process, then Apple’s beta programme is something you should consider. This initiative allows developers and public beta testers to gain access to the updates before they’re released, so they can help test for bugs and give any new features a thorough workout before they’re unleashed on the general public.
WWDC will take place soon and following the keynote on 6 June Apple will probably release the first developer betas of iOS 16 and macOS 13. If you are keen to get involved in testing the new software – and any other Apple operating system – read on to find out how to apply.
In this article we explain how to get involved with testing the betas, but also point out some of the reasons why you may wish to give it a pass and wait for the final versions of iOS 16, macOS 13 and others to arrive.
As the name suggests, this is a chance for volunteers to download a beta version of the new operating system for their device and test it out. It’s completely free and you can sign up for the following software:
The idea is that you install the pre-release software and use it as you would your normal OS and send Apple comments through the built-in Feedback Assistant regarding crashes or other behavioural anomalies that you encounter when testing your apps, or when using the software as you would normally.
It comes in two flavours – Public and Developer – with the latter including some extra options that we outline below.
The first developer beta of the new version of macOS will arrive following the keynote on 6 June.
Developer betas are, as the name suggests, only for app developers. The public beta version of macOS, which anyone can try, is likely to arrive a few weeks after WWDC: we’d expect it to drop around mid July 2022.
As with macOS, the first developer beta of iOS 15 will arrive after the WWDC keynote on 6 June.
The first public beta of iOS 16 is likely to arrive in late June or early July.
For the four operating systems mentioned at the top of the article (watchOS is slightly different), Apple offers two types of beta. The developer beta is available to any paid member of Apple’s Developer Program. You can enrol as a developer here. It costs $99 a year.
There also a free public beta testing programme that’s free and open to anyone with a valid Apple ID (iCloud accounts qualify) who goes to the Apple Beta Software Program page and signs up.
You’ll obviously need to agree to the terms and conditions. Be sure to read them first, as participating in the programme can open your device up to code that has the potential to cause trouble with its functionality.
Depending on whether you are joining the Developer Beta Program or the Public Beta you may also have to abide by an NDA. Be aware that releasing details of what you’re seeing in the beta may be breaking the rules.
Apple
There are a few reasons why becoming a beta tester for the next version of iOS or macOS might seem attractive.
For a start you might gain bragging rights for being one of the first to use the new software. However, Apple regards the programme as confidential, so you won’t actually be able to blog or post on social media about the features or problems until Apple itself makes them public knowledge.
Becoming a beta tester also gives you a chance to shape the development of the software – your feedback could be invaluable in stopping a bug or just generally improving the quality of the software on your Mac or iPhone. You will be providing a service to others in ensuring that all bugs are ironed out before the final release.
However, beta software, by its very nature, is unstable and it’s worth noting that participating in Apple’s macOS Beta Seed Program is not a light undertaking. You should consider whether it’s really right for you before downloading and installing the pre-release software, which is bound to have bugs and issues that could cause things to go spectacularly wrong with your Mac.
This won’t be helped by the fact that Apple is not obligated to provide any support for pre-release software.
If you only have one Mac, and you’re intending to run the pre-release software on that machine, you might want to reconsider. Apple suggests that you should run the pre-release software on a dedicated Mac, not a Mac that you use for business or production purposes.
This means that we would heavily advise against putting it on a device upon which you’re reliant. Bugs in the code could see the device stop working at any moment or in worst case scenarios it could actually brick your machine, leaving it a very expensive paperweight.
If you don’t have a spare Mac to hand at least consider installing the macOS beta on a separate volume. Or you could run the beta on an external drive.
Similarly if you don’t want to be stuck without a working iPhone don’t install the beta of iOS on yours. If you have an old iPhone handy that might be a better option for running the new iOS (if it’s supported).
Luckily participating in the beta programme doesn’t invalidate your warranty, so if something does go wrong, a trip to the Apple Store would hopefully see it rectified.
The threat of bugs and other stability issues is a good reason to think carefully about whether you want to take the risk of using the beta. If you do decide to install the beta software, make sure that you create a full backup beforehand. Read Best backup software for Mac and How to back up an iPhone or iPad for some ideas on how to do this safely.
Also, remember that installing software can take a good few minutes – if you don’t have time to wait for 20 minutes every few weeks while your Mac installs the latest version (especially if that’s only going to break everything for you) you might find the frustration outweighs the novelty value of having the latest updates.
There’s also the important matter of privacy. By agreeing to test the macOS beta software, you’re essentially giving Apple permission to collect diagnostic, technical and usage data from you, unless you go through the process of opting out.
For example, the first beta version of Mac OS X 10.10 Yosemite came with several known issues, including problems in Safari while trying to access Netflix content, iPhoto, Photo Stream and iCloud Photo Sharing problems, iCloud Drive issues and AirDrop issues, so beware. In another example, early beta versions of macOS High Sierra attempted to use AFPS (Apple’s new file system) on Fusion Drives. This feature was later removed, but those people who had already installed the beta had to perform a complicated uninstall process and revert their Fusion Drives back to the previous file system.
If you install the beta and then think you made a mistake, here’s how to revert to an older version of macOS. We also have a guide to removing the iOS beta.
It’s free to join the Public Beta. Developers get the developer version beta for free – but they need to have signed up to Apple Developer Program ( here), which costs $99 a year.
No. This is strictly a voluntary pursuit.
The Developer Beta is usually a few steps ahead of the Public Beta, which essentially means that the Public Beta will be slightly more stable.
The Developer Beta normally comes out after the WWDC keynote presentation. There is usually a slightly longer wait until the Public Beta arrives.
However, once the programmes are under way there is usually only a few days between the developer beta being released and the public version arriving.
While the Public version is aimed at the user experience, those who develop apps for Apple products can use the Apple Developer Program to gain early access to the beta software and be able to implement the necessary changes into their code so that apps are ready to go when the full version of the OS is released.
There’s also the TestFlight platform which enables developers to invite up to 10,000 users to give their in-development apps a trial run. Plus, Apple provides a range of software tools such as Xcode, CloudKit Dashboard and many others.
The purpose of the beta program is to provide Apple with feedback about the upcoming OS. If you experience bugs or other issues, report them to Apple using the Feedback Assistant app. And don’t just say something crashed, explain exactly what you were doing when the crash happened and try and reproduce the crash to see if you can identify what steps lead to it.
Don’t just tell Apple that you don’t like the ‘flat’ look of the user interface. Your purpose as a beta tester is to provide feedback on bugs, not try and assume Apple’s software designer’s role.
That said, it won’t always be bugs you need to provide feedback on. Perhaps you can’t work out how to do something and a user interface tweak is required.
You can also provide feedback if third-party apps aren’t working as they should – there is actually a 3rd-party Application Compatibility category in which to submit feedback.
Expect there to be bugs and issues in the beta – the versions of macOS available through the Beta Software Program are not finished products, by installing it you are agreeing to become a tester and helping Apple to iron out these issues.
Registered Apple Developers are able to download pre-release versions of most of Apple’s software too, but it costs $99 (approx £74) per year to register as a developer.
To register as a developer head over to the Apple Developer Program registration page and click Enroll. Registering as an Apple developer will give you access to support materials, and enable you to register Macs and iOS devices with Apple so you can use them to run your software.
You can sign in with your own Apple ID (recommended if you’re a single developer), or you can create an Apple ID just for the developer account (recommended if you are developing for a company).
You don’t have to pay Apple to register as a developer. You can sign up and gain access to all the developer tools without paying a penny. The basic registration is fine for developing and testing an app, although you will need to sign up with Apple for membership if you want to download the developer previews.
If you are a member of the public you can also run the beta – but each version of the beta comes a little later than the developer version. Apple tries to make sure the worst of the issues are ironed out before it goes on wider release. That’s why there are often a number of weeks between the first developer beta and the first public beta being released. You can also expect a delay between each version of the developer beta and the matching public beta arriving.
To sign up you’ll need to go to the macOS Beta Seed Program website. From there, you can find out more about the program by clicking Learn More or FAQ.
You must be aged 18 or older with a valid Apple ID, and you’ll also need to be willing to accept the Confidentiality Agreement, which means you agree not to share information or screenshots of the update.
By clicking ‘Get Started’ on the macOS Beta Seed Program website, you’ll be taken to the ‘Sign In’ page. If you don’t already have an Apple ID, you can create one by clicking ‘create one now’ in the grey box on the left. If you do have one, however, you can go ahead and sign in using the password you normally use for your iTunes and other Apple services.
Next, you’ll be taken to the macOS Beta Seed and Confidentiality Agreement. You’ll need to read the agreement (you can view it as a PDF if you prefer by clicking the link beneath the scroll link) and then click accept. Unless of course you don’t agree with the terms in which case you’ll want to stop the registration process now.
Once you are registered for the Apple Beta Software Program you will need to enrol your Mac here in order to be able to get the updates from the Mac App Store. You will have to re-enrol your Mac if you had previously been a tester.
You will find a download link and your redemption code on that page. Click on the link and enter your code to download the latest beta.
But hang on, there are a few things you should do first, not least be absolutely sure that you want to run the beta…
Here are the steps to follow to sign up for the public beta:
Note: When you purchase something after clicking links in our articles, we may earn a small commission. Read our affiliate link policy for more details.
Macworld contributor Martyn has been involved with tech ever since the arrival of his ZX Spectrum back in the early 80s. He covers iOS, Android, Windows and macOS, writing tutorials, buying guides and reviews.
Macworld contributor Martyn has been involved with tech ever since the arrival of his ZX Spectrum back in the early 80s. He covers iOS, Android, Windows and macOS, writing tutorials, buying guides and reviews.
Nenhum comentário:
Postar um comentário