Mobile strategy is important for any Internet business, but it’s also a challenging market to operate in. At Myna we’re trying to make it a bit easier. Over the next few weeks we’ll be extending our real time A/B testing technology to mobile, giving Internet businesses unequaled ability to understand and optimise their offerings across the mobile and desktop Internet.
Compared to the web, mobile business is hard. Consider the following:
- Ranking is everything on both the iOS and Android app stores. Downloads quickly drop off as ranking falls.
- New apps have a short window when they are highly ranked, and if they can engage with users during this period they can maintain their ranking.
- Users hardly ever update their apps. Furthermore, if you’re targeting iOS, the lengthy App Store review process ensures that fixes are too late to have a significant effect.
- Limited data, only the total number of downloads and app store feedback is available.
This means that most businesses targeting mobile get only one chance to get it right — when they first launch — and they have to build their product before they receive any real feedback. Anyone who has run a business knows that nothing destroys assumptions faster than real users. In the last decade, online businesses have learned how to deliver steady improvements through controlled testing and rapid iteration. Can mobile businesses do the same?
We’re not the first to recognise the need for fast iteration in mobile apps. Trigger.io, Phonegap, and others provide HTML5 frameworks for building apps that are essentially websites. This allow updates to be pushed straight to mobile devices, a process known as hot deployment. Developers gain a fast feedback cycle, and they can use familiar analytics and testing tools, including Myna, to optimise their application. However, this approach cannot match the look-and-feel and performance of a true native application, which rules it out in many cases.
We’ve heard from a number of existing customers about their frustrations testing on mobile, and have decided to address it directly. We’re developing native Myna clients for iOS and Android, and also extending our API to allow you to push changes to your tests straight from Myna’s dashboard. This gives the best of both worlds: native application performance and hot deployment, bypassing the issues with app store updates.
We’re very excited about this new addition to Myna, which will benefit our existing web users as well. Myna will become the first testing platform that allows cross-channel testing, backed by super-fast bandit algorithms.
We will be launching Myna for mobile in closed beta. If you would like to be one of our beta testers you can sign up by emailing email@example.com.
We’re pleased to announce that we’re finally coming out of beta, which means the introduction of our least-requested new feature: pricing plans. These will come into effect on 15th December.
We’ve got plans for all sizes of business and website, including a permanently free plan for low-volume users or sample tests. Sign up now and start A/B testing for free - you can upgrade whenever you’re ready.
All our existing beta users (and any new sign-ups) will have the opportunity to choose a plan before December 15th. On that date, everyone else will be transferred onto the free plan. Don’t worry! All existing tests and data will remain intact.
We’ll make further announcements on billing closer to the time, but for now, all the details are available on the Myna pricing page.
(…and bloggers, authors, and web admins…)
We are pleased to announce the launch of Myna for HTML – a simple new way to integrate Myna on your web site using 100% pure HTML. No coding required!
Up until now, integrating Myna has required some coding knowledge. This meant Myna was excellent for developers but posed a barrier for people who don’t code.
All that has changed – Myna for HTML is integrated directly into our dashboard so absolutely no programming is required. All you need is a little knowledge of HTML and CSS and a burning desire to optimise your website. (A Myna account will come in handy, too.)
Using Myna for HTML is a simple three-step procedure:
- copy-and-paste a snippet of code from our Dashboard;
- tag up your variants and conversion goals using HTML 5 data attributes;
- there is no step 3.
Just a quick post to let you know that there’s now a client library available for Python.
It uses the built-in
httplib to allow you to suggest and reward your Myna clients. It has no external dependencies and has been tested in Python 2.7.
Here’s a link to the github repository, which includes some basic documentation so you can get started. We’ll add some more detailed information to the main site pretty soon.
Earlier in the week, we sent out a short survey to our awesome beta testers, asking them what they would most like to see added to or improved upon in Myna.
One of the common responses was a request to improve our documentation. So, we’ve done it, and you can access the new and improved documentation from the ‘help’ tab above, or from this handy link.
We’ll continue working on the documentation to make sure it’s as complete and helpful as possible. We hope that this initial change will make it easier and faster to start A/B testing with Myna.
If you have any comments or suggestions regarding the documentation (or anything else), please let us know using our contact form.
Myna’s new API is out! A lot of discussion went into the new API, so it took a bit longer that we planned. We think it’s worth the wait &emdash; the new API is far richer and more usable than our original design. If you want to integrate Myna into your existing marketing systems, you’ll definitely want to check it out. Also take a look at the clients under development on our Github page, which will make integration easier.
We’re currently working on a new API for Myna. The new API exposes much more functionality, allowing, for example, experiments and variants to be created and removed. While it’s in development we’re soliciting feedback from the community. If you’re interested, read the documentation and let us know about any changes you think would improve it.