Native Applications
Native applications are a core element of the 360o Marfeel solution.
The users that demonstrate brand loyalty by downloading and using a publisher's app, or, power users as they're also known, statistically spend a lot more time within a native app, driving engagement and the related revenue performance to optimal levels.
It's vital that publishers be able to provide this option to their dedicated audience to leverage the increased session time and monetization capability it provides.
The Marfeel offer
Marfeel provides native apps as part of its 360o solution to magnify a customer's publication and boost engagement and revenue by targeting all available channels.
Native apps are provided to all Marfeel customers upon request after one month of activation as a complement to their Marfeel mobile site.
Marfeel waits for a month after activation in order to ensure that the mobile site is generating the optimal revenue predicted, and that all features that were developed for the publisher's mobile site are running seamlessly before efficiently developing a native app.
The development process
Certain steps in developing a native app can be quite complex. For this reason, Marfeel removes the complexity for publishers and develops it on their behalf.
However, the process may be different depending on where the app needs to be developed, and the possible accesses required to different Google and Apple systems.
For details regarding the steps involved according to each scenario, click one of the links below:
- The app is being developed and registered in the partner's App and Google Play stores
- The customer's app is being updated with the Marfeel version in their App and Android store.
Developing an app in Marfeel's app and android store vs the customer's
The difference between developing an app in Marfeel's App and Android store instead of the customer's is:
- When the app is developed in Marfeel's stores, it's uploaded with Marfeel's certificate. This expedites the development process and prevents any possible delays waiting for the publisher to acquire a certificate to upload and distribute apps.
The publisher also avoids having to pay for a developer account. - When an app is developed in the customer's stores, it's uploaded with the customer's certificate which requires a developer's account.