![]() How can you update app features without sending a new version to the app stores? Mobile development teams can limit the blast radius when bugs arise, avoid fire drills, iterate, and validate new features with real users in real-time. The Optimizely UI allows feature toggling, gradual rollouts, tests, and updates without additional code deployments. Or it could mean updating how the feature behaves when enabled for said groups. Remotely configuring a feature can mean enabling functionality for internal testers, beta groups, regions, premium users, or a percentage of your entire audience. ![]() Feature flagging and remote configuration mitigate these risks. Nobody wants a bug or a poor-performing feature tanking metrics and spurring negative app store reviews. ![]() Ideally, errors are detected before you submit to the app stores, but it’s nearly impossible to replicate every possible scenario that occurs out in the wild. What can feature flagging do for mobile development teams?įeature flags allow you to roll back, or suppress, app code without additional app store updates. Below are the key points from the session, which showed how Optimizely enables mobile development teams to manage features and experiments without extraneous app store updates. He also demonstrated how to use the IDE plugin to integrate feature flags and experiments more efficiently in Android Studio. Recently, Tom showcased his work in a mobile development session, where he explained how Optimizely’s iOS and Android SDKs work. ![]() He built an IDE plugin, making it easier for developers to use Optimizely in all IntelliJ based products such as AndroidStudio, IntelliJ, GoLand, and P圜harm. Optimizely Engineer, Tom Zurkan is all about efficiency.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |