If you are a Mag+ customer with a 4.X app and want to upgrade to 5.0, this article will serve as a quick guide to the things you need to know before building and submitting your update. As with any big update, there are some key differences in the new apps, so walking through the things below will help ensure a smooth transition.
Changes in 5.0 that Require Action
- Banners you have uploaded to your 4.X apps do not move automatically to 5.0. You will need to upload them again, and note that sizes of the banners have changed slightly. Read more about In-app Store Banners.
- If you want to change banners in your 4.4 app (for those who have not upgraded to iOS7 and therefore cannot upgrade to 5.0), let us know and we'll activate a new option for you under your Apps tab called Legacy Banners. Changing banners in the regular Banners section will only affect your 5.0 app.
- Since subscriptions can now be purchased through Banners, the Featured Issue space, and on every issue preview, subscriptions do not, by default, appear in the issue grid. If you want your subscriptions to appear in your app's issue grid, you must check a box in the Subscriptions tab called "Display in Issues Grid".
- Required app icon sizes have changed, so you must upload new icons before you can build your app. Read more about building your app.
- If you have customized icons in the bottom menubar of your 4.X app, note that you can no longer customize the full button in 5.0. You can only upload a new icon, and change the displayed text under Apps -> Customizations -> Applications Texts.
- If you have customized the text strings in your 4.X app, you must redo those changes as 5.0 has a different strings file. You can find the new strings file in Apps -> Customizations -> Application Texts. Download the sample file, modify it and re-upload it, as you did before. Note that this will not affect your 4.X app.
Note: Android now uses a strings.xml file for application text customization. It is not the same file as is used for iOS, therefore you must customize it separately. The strings.xml file can be downloaded from the Mag+ Publish Portal under Apps -> Customizations -> Application Texts.
New Features Available in 5.0
- Banners can now be clicked to trigger a subscription purchase or an issue detail (as well as launch a URL). Read the article 8 Smart Ways to Use the New 5.0 Banners.
- Banners now span the full width of the device screen and can be different heights.
- You now have an optional Featured Content space in the Issues interface where you can highlight an issue or a subscription. Read more about the new in-app storefront and Issues space.
- Preview images are much more important as every issue now has a preview option in the in-app store. Read more about including Issue Previews.
- You can now include bonus issues with a subscription. Read more about subscription inclusive issues.
- A new third-party service, Oplytic, allows you to track the success of your app marketing campaigns. Read more about Oplytic.
- Android apps now support nearly all creative features from iOS, including slideshows, popups, and panning and zooming blocks. Read more about the remaining differences between iOS and Android apps.
- Popups can now have links on them, and can now be any type of content, including HTML or slideshows. Read more about the new popups.
- Android can now build true single-issue apps. Amazon, like Apple's App Store, allows issues to be bundled directly into an app. Google Play, however, does not. To build a single-issue Google Play app, Google must host the issue content as an app extension. Read more about configuring single-issue Android apps.
Things to Note
- Apps have different customization options in 5.0. Read more about building your app.
- Appboy Newsfeed and Feedback are now dedictaed buttons and fullscreen spaces. (Note that the Appboy Newsfeed content does not yet span the width of the screen, but will after our March 4th release.)
- Setting an inclusive issue now triggers a popup, so this feature can be useful for free issues, too. Read more about inclusive issues.
- If you used Amazon "App Identifiers" or "Certificates" different than those used for Google Play, you will need to contact us to reactivate a separate Amazon configuration. See the section below on "How to Contact Mag+."
- If you see only one button for building an Android app, that one app can be submitted to both Google Play and Amazon. If you see two buttons (one to build for Google Play and one to build for Amazon) you will need to press both and submit the corresponding app to the appropriate marketplace. You will only see two buttons if "Separate Amazon Configuration" has been reactivated for your brand (see above), and/or you have configured in-app billing for your Android app.
How to contact Mag+
- Visit the Mag+ Help section.
- If not logged in, click the "Login" link to enter your username and password.
- Use the "Submit a Request" link that appears in the top bar to fill out a request form.