Implementing a mobile solution requires input from many stakeholders. With so many options available – m.dot, responsive, adaptive – it’s important that developers review the solutions from a technological standpoint. After all, they’re going to be working with the technology the most on a day-to-day basis.
Developers are often the most hesitant to implement third party mobile solutions, and with good reason, the chosen solution will have a major impact on them if it isn’t successful. On the other hand, a winning solution could make their jobs easier and allow them to have a bigger impact on the company’s success. To address these concerns, we spoke with Deus Duke, the mobile development lead at Tria Beauty, to understand what his experience has been working with Mobify from a developer’s standpoint.
What pushed Tria to get a different mobile solution?
The duplication of effort meant we were wasting resources, and synchronization problems created an inconsistent shopping experience for our customers. At that point, we knew we needed a more robust mobile solution as mobile traffic was increasing daily.
What has your experience been like working with Mobify?
I like the instant gratification of it. Being able to jump into Mobify, throw on a tag, set up a template really quickly and I’ve already got the beginnings of the site and I can start using the bits and pieces that I need. On the other side of that, I’m able to work very efficiently, by myself or with a small team, without having to rely on a whole bunch of developers and having to bring new people on and train them.
What was the learning curve with the technology?
The technology is pretty straightforward and easy to learn. It allows me as a developer just to build, even if it’s a prototype or something that I want to show. It’s very fast which enables me to focus on things other than building out the core of a mobile site; I can focus more on the front-end.
What mobile challenges did Tria face before implementing Mobify?
We would design user experiences for desktop first and not necessarily think about how it would affect the mobile experience. New products or new page templates would ship on desktop and then mobile would follow a week or two later, sometimes even longer. We also had problems synchronizing the different cart flows because mobile had a completely separate cart flow – but they still had to talk to the same back end.
What results have you seen working with Mobify?
I have seen a massive surge in mobile traffic since working with Mobify, it is now well over 50%. We brought on Japan in about a month and then Korea in about a month or less. The day after we had launched the new templates, the conversion rate shot up to 3%, which was over a 300% increase overnight.
What’s your advice to other mobile developers?
If you’re planning to build your own mobile site, I wouldn’t do it. I’d check out Mobify. It’s fast, and efficient and incredible what you can do with limited resources.
Download the Tria case study to share with your development team.