A colleague and I are building an App which will be distributed via the App Store but we want it to have AppConfig functionality so basic settings within can be pushed to the app via an MDM server if the app is on a managed device.
Is this at all possible or is that functionality reserved purely for enterprise deployed applications?
We're having a hard time getting our heads around any of the documentation. It seems like what we're trying to do might be possible but we cannot figure out how. There is so little info on MDM device management about seeing as it's relatively new to the iOS scene.
The example app that Apple provides which demonstrates MDM AppConfig. Can only be tested on an enterprise account, however surely if that functionality is added to an AppStore distributed IPA then there should be no reason why it can't receive an updated plist via push...right? Or is there some kind of additional code signing/provisional pairing happening here which is only active once an App has been installed on a device via an ad-hoc/enterprise deployment?
If it is limited in this way it seems pretty unusual, especially seeing as there are some institutions out there who would no doubt like to buy an App and then adjust some of it's settings in house.
Hopefully someone here has some answers for me, as all of my searching so far has drawn a blank.
Is this at all possible or is that functionality reserved purely for enterprise deployed applications?
We're having a hard time getting our heads around any of the documentation. It seems like what we're trying to do might be possible but we cannot figure out how. There is so little info on MDM device management about seeing as it's relatively new to the iOS scene.
The example app that Apple provides which demonstrates MDM AppConfig. Can only be tested on an enterprise account, however surely if that functionality is added to an AppStore distributed IPA then there should be no reason why it can't receive an updated plist via push...right? Or is there some kind of additional code signing/provisional pairing happening here which is only active once an App has been installed on a device via an ad-hoc/enterprise deployment?
If it is limited in this way it seems pretty unusual, especially seeing as there are some institutions out there who would no doubt like to buy an App and then adjust some of it's settings in house.
Hopefully someone here has some answers for me, as all of my searching so far has drawn a blank.