We are excited to announce the new AppWarp Dashboard with a fresh look and feel. With this release we have given more control to the App admin with increased usability experience.
By default, the AppWarp Users will be landed on the new UI, however they always have an option to switch back to old UI, if required. When you login to AppHQ Console, you can select AppWarp from drop-down to switch as shown in Figure-1.
App42 Push Notification now supports WNS (WIndows Push Notification Services) for Windows Runtime Apps. This will enable sending toast, tile, badge and row updates from App42 to your Windows Runtime Apps.
Before you can send notifications using WNS, your app must be registered with the Windows Store Dashboard. This will provide you with the credentials for your app that your cloud service will use in authenticating with WNS. These credentials consist of a Package Security Identifier (SID) and a secret key.
So, your app is already live – what next? Yes, you need to figure out a way to continuously engage and convert your users and the answer is a Mobile Marketing Platform!
In times when user behavior changes with every second, you need to keep a check at every level on how your app users are reacting. Not only that, you need to have a trick up your sleeve for every checkpoint, in the sense, how you go about engaging them at each juncture.
Ever since the debut of Marketing Automation there has been a sudden thrust of methods through which all the app marketers/promoters have started market their apps according to the behaviour of their users. Though, not many are very clear on how to use these tools to acquire more users and engage the existing. We have taken the initiative to lay open our secret book of marketing automation and we will be live not just one but on two days as we do a webinar on 10 key metrics you should track as an App Marketer. Continue reading
App42 Unity SDK is now equipped with offline storage support which allows your app data to be saved in local storage in case of unavailability of network/server. Offline storage syncs it with server later when network is available. This is useful in many scenarios such as if your user is playing a game and has scored on completion of a specific level. However, at the time of posting if network is not available his score might get lost and his efforts will go waste. This can be avoided using offline storage where his score will be saved locally in case of network unavailability and will be later synced with server when network becomes available.
You can enable this feature with single line of code without any additional cost. You can read our tutorial about more details. Please feel free to write any questions/feedback at firstname.lastname@example.org regarding the same.
Push Campaign is an ultimate tool for all mobile app marketers to increase engagement. Push Notification brings back users to your app repeatedly and consistently, it provides timely and relevant information to the targeted audience. When we say timely and relevant information, it means these Push Notification Messages are driven by certain rules over a carefully segmented target (Segmented) Audience. This is usually driven by running Automated Push Notification Campaign by an app marketer. If you are not sure, which type of campaign you should run for your app to increase engagement and monetization, here is the list, which will help you to choose and get started with setting up Push Notification Campaign for your app. Continue reading
App42 platform now provides a way to track effectiveness of Push Notification Campaign that you are running for your app users. This can be tracked for campaign as well as on-demand-push being send from Console/API. You can define name of the campaign at the time of sending push notification and can see its effectiveness(Open Rate) in Push Dashboard. Continue reading
Many of our customers have written custom codes and encountered performance issues once they hit the production—especially their custom code was throwing error code 1904 (Execution Time Threshold Exception). Code written inside any custom code must get executed within 10 seconds otherwise it will get killed and client will receive 1904 error code with execution time threshold exception. There are a few guidelines explained below that will help you in optimizing your custom code so that you can avoid these time-out exceptions.