What is our primary use case?
Jamf School serves as my MDM solution for managing iOS device testing and enterprise app development. It has been instrumental in helping me push internal builds, manage app configurations, Wi-Fi, and certificate profiles to test devices without manual setup.
For the payments SDK's flow, particularly Apple Pay and app switch scenarios, Jamf School has helped me validate how apps behave on supervised and managed devices where restrictions, VPN certificates, or app policies may affect the flow. This has been especially useful in testing certificate-based authentication, zero-touch device provisioning, and remote app updates.
I am using it directly in my project and interact with the public cloud-hosted environments for the APIs and tokenization services. As a developer, this helps me validate that the SDK communicates with the cloud-hosted backend. I am currently using it in the cloud-hosted environment only, but in my private project.
What is most valuable?
The best features that Jamf School offers are the enterprise restrictions, device wipe and re-enrollment scenarios, and app development at scale.
In my daily work, Jamf School has reduced the manual, repetitive device setup. Instead of configuring Wi-Fi certificates, VPN, app installs, and restrictions manually on every iPhone, the device is auto-enrolled with predefined policies. This has saved quality assurance and developer setup time, improved consistency across test devices, and helped reduce customer enterprise issues faster.
I find that the certificate profile updates, device trust, and VPN profile validation are a great combination.
What needs improvement?
I do not currently have a scale in which I have measured these parts, but I can tell you it has really saved a significant quantity of hours with onboarding speed and regression efficiency. I can say that Jamf School has achieved 70 to 90% time savings through automated enrollment and Wi-Fi certificates, which represents 90% less time on provisioning and ongoing device management.
If I provide a comparison, before Jamf School, manual device setup per device included app install time of three to five minutes, test enrollments of five minutes, and certificates altogether taking 20 minutes. After Jamf School, with automated policy and environment, the overall process can be completed in three to five minutes. I believe the speed is quite perfect. I do not think there is currently any improvement needed for this aspect. If I use it further in three to four months, I will be able to tell whether any improvement is required.
For how long have I used the solution?
I have been using Jamf School for the past two months.
How are customer service and support?
I think the documentation is also quite clear.
What other advice do I have?
I have used Jamf School in my current personal projects, not for my organization.
As I mentioned, it has really reduced the manual setup time and has enabled faster regression testing. Now, quality assurance and developer setup require less time because they can all auto-enroll in the predefined policies.
It has truly helped me. The amount of time it has reduced, for example, while I was making payments in iOS apps for Apple Pay, Venmo app switch certificate, or in enterprise restriction scenarios, Jamf School has reduced the time needed to prepare edge case devices, which directly improves the turnaround and issue reproduction speed.
I work extensively with the public cloud-hosted APIs and environments, so it involves my daily network. From my organization, if I check, my company basically uses the Microsoft enterprise infrastructure, which is likely the Microsoft Azure part.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other