Itâs a challenge that haunts just about every digital innovator these days: when youâre pushing your product out on multiple technology platforms like iOS that are changing on a quarterly or even weekly basis, how do you keep up? What code or platform can you use safely, without fearing that it will break with the next Android iteration, leaving your users and customers with a broken app â and a bad experience that can hurt trust in your brand?
We chatted with Sidebuy CEO and founder Mona Akhavi, speaking this month at Tech Vancouver on May 31, about these very issues. Sidebuy is a fairly new startup that matches bloggers to brands, helping them monetize their content. Itâs a platform for which there seems to be a pretty large market need involving thousands of digital influencers â but putting it together required a lot of deep thought early on about the right mix of technology to build it.
âMy methodology has always been to build just enough of a minimum viable product so you can learn from how people are using it in the market.”
âWhen you choose the type of programming or system architecture youâre building on, youâre using what developers are talking about at that time, because there is talent available for it,â Akhavi said. âBut one thing many people donât look at regarding product is how the product is going to evolve in terms of the roadmap. Is it going on to the web? On to a mobile device? A virtual reality headset? How will that evolve? It should affect the choice of technologies right now, which is how youâll be able to iterate.â
Of course, for many companies, seeing more than a few quarters down the road is hard. Thereâs a tendency to rely on solutions that worked before â and that has consequences. âItâs not an easy thing to do for a lot of product managers, CTOs, and technical people who are biased and comfortable with a particular architecture or stack theyâre used to using,” said Akhavi. “I see it happening constantly â a quarter after starting to build something, they just say theyâre going to rebuild the product from scratch because itâs not scalable, or wonât connect to smart TVs or wonât connect with a mobile app. This creates a lot of sunk costs.â
Even the biggest projects for some of the most innovative organizations in the world can fall prey to this, so it pays to be adaptable. When Akhavi was part of the digital operations team with the CBCâs Olympic Sochi Project, building a mobile app streaming live results, providing games and a free portable experience, she started planning two years ahead. âOver 12 to 18 months, there were three different iOS operating systems, two different Android systems, three different screen sizes for LG, then the iPad and competitors came out â and I had to track all of that. Each evolution caused a different situation.â
The key to maintaining focus and quality was maintaining good relationships with the apps stores so they could get quick approval, and putting team members in a position to be able to see what was coming. âAs part of this, we would send team members to go to conferences where the ârulers in the tech worldâ would give a preview of what was coming, so we would know what was coming and plan for it. Itâs an art and science to keep on top of it all.â
For startups looking to avoid these issues, itâs the Lean methodology to the rescue, again. âMy methodology has always been to build just enough of a minimum viable product so you can learn from how people are using it in the market. Let people use it. In three months, there will be new mobile, new VR, or new iOS systems coming out â so donât pre-build if youâre not sure what you have to iterate on.â