Modifying apps that have frameworks that don’t allow bundle ID changes can potentially lead to application errors if these modifications are not done properly.
This Knowledge Base article summarizes how Appdome automatically detects when certain frameworks do not allow bundle ID changes in advance, thereby avoiding potential error conditions which may otherwise have occurred.
We hope you find it useful and enjoy using Appdome!
Using a simple ‘click to add’ user interface, Appdome allows anyone to easily enhance an app with frameworks that don’t allow bundle ID changes – instantly, no code or coding required.
Using Appdome, there are no development or coding prerequisites. For example, there is no Appdome SDK, libraries, or plug-ins to implement. There are no additional development requirements to Fuse a mobile app that will not accept bundle ID changes with additional features and integrations. The Appdome technology adds relevant standards, frameworks and more to the app automatically, with no manual development work at all.
In order to use Appdome’s no code implementation to modify apps that don’t allow bundle ID changes, you’ll need:
Select the Build Tab. Beneath it, you will find several service options. Select the ones you’d like applied to your app then Build My App!
Congratulations! You now have a mobile app fully integrated with the features you selected even when it didn’t accept bundle ID changes.
The technology behind Build My App has two major elements – (1) a microservice architecture filled with 1000s of code sets needed for mobile integrations, and (2) an adaptive code generation engine that can recognize the development environment.
Appdome is a full-featured mobile integration platform. Within Context™, Appdome users can brand the app, including adding a favicon to denote the new service added to the app.
For more information on the range of options available in Context™, please read this knowledge base article.
In order to deploy an Appdome Built app, it must be signed. Signing iOS apps and Signing Android apps are easy using Appdome. Alternatively, you can use Private Signing, download your unsigned app and sign locally using your own signing methods.
Once you have signed your Appdome-Built app, you can download to deploy it using your distribution method of choice. For more information on deploying your Appdome-Built apps, please read this knowledge base.
For more information on this topic, visit Appdome for Enterprise Mobility on our website.
If you have any questions, please send them our way at firstname.lastname@example.org or via the chat window on the Appdome platform.