We're exploring how you can maximise the results you get from your Pugpig app via experimentation.

Many of our customers will be familiar with running experiments like A/B tests on their websites, which can often be facilitated by fairly simple drop-in solutions. Historically we've not seen an appetite for carrying this over into our apps, however as publishers are increasingly seeing their apps as important acquisition channels, rather than purely a retention tool, we are hearing more and more interest.

We're kicking off a piece of work to explore how we can best support customers' goals through A/B testing. We'd love to hear from you if this is something you are interested in. Here are some questions we'd be keen to hear your thoughts on:

• What kinds of hypotheses/changes/areas of the app would you want to be able to test? 
• Do you already have expertise in-house on running experiments and analysing the outcomes? 
• Do you already use a third-party tool on your website, and would you want/need the same tool to be available for in-app A/B testing?

Please feel free to drop Emillie an email via support on these questions, and any other thoughts you have: support@pugpig.com

We will be evaluating the best approach both in terms of meeting our customers' needs, and also from a technical feasibility perspective. We may add support for a third party such as Optimizely, or we may add the capability via our existing ability to remotely update our apps' configurations on the fly - potentially then feeding into Mixpanel, our product insights tool, to present results. A drawback of the former approach might be the cost to our customers of engaging with the third party service, but on the other hand tools like this can offer best-in-class features and expertise.

Note: Whatever approach we settle on we expect to be offering the ability to A/B test app elements (e.g. paywall copy/button colours etc) rather than anything in your content. Although we'd still like to know if that's something you're interested in