Should Your Mobile App Shutter Your Web Site?

Last week, Flipkart, India’s largest e-commerce firm, and its fashion subsidiary Myntra, announced that they shuttered their mobile Web sites. According to the article, which has a good analysis on zdnet, their desktop Web site is still active, but they are considering shutting that down as well.

Indeed, if you go to flipkart.com or myntra.com from a desktop browser, the site works just fine. Change your User-Agent to iOS or Android, and you get a link to their platform-specific mobile app.

One of my favourite VC bloggers, Fred Wilson, popularized the term “mobile first“, wherein a company develops for mobile before going for the desktop/Web (if ever). Yet, Flipkart, a well-established company – the Amazon of India – which already has an existing heavy Web presence, tailored for both desktop and mobile, is shutting down their mobile Web and possibly desktop Web.

Why are they doing it, and what are the risks?

Why Did They Do It?

The apparent rationale is provided by Myntra. According to the head of their e-commerce platform, 90% of their views and 70% of their orders come from mobile apps. While he doesn’t delineate what that is in terms of revenue percentages, and clearly there is a somewhat higher order rate per view on Web vs. mobile app, a CEO or Board looking where to invest serious engineering money will read those numbers and say, “double-down on the 90%.”

Another factor is that Flipkart suffered some serious Web downtime during the Xiaomi launch in July 2014, and possibly other issues throughout the year. When 10% of your visits, or 30% of your orders, gives you 80% or more of your grief, it would be rational to move customers away!

What Are the Risks?

There are 2 categories of risk here, technical and business.

On the technical front, there are several issues.

  1. Kicking the Can: I get it, their Web site went down. But an iOS or Android app is not Web-free. It just uses a clear subset of the Web site, the application interface, or API, most likely a REST type, which is accessed… over the Web! Their Web site, rather than using just the API, does all of the work the API would do plus it renders all of the page visuals. A mobile app eliminates only the rendering of the visuals, not the underlying logic. Without digging deeper, it is impossible for us (or them) to know if the problem is in the rendering, in which case going pure app will help, or in the underlying processing, in which case the problem will recur sooner or later.
  2. It is Solvable: Even if the issues are only in the rendering, there are technologies that can solve the issues, such as single page applications (SPA), content distribution networks (CDNs) and others, all of which depend on correct application architecture.
  3. Loss of Skills: In choosing to disinvest their Web site, Flipkart risks losing the skills that they have in-house and the learning they have amassed. If they were just a data-provisioning company, one that connects directly to business platforms or developers, then the user flow, user interface, design and user technology skills would not matter that much. But Flipkart is not; they are a consumer-facing company, with real people using their service. Their continued success depends on people happily using that service. Should they need to return to the Web, they will be lacking in key skills.

But more important than the technical risks is the one big business risk. They are gated.

The beauty of the Web always has been free access. You can access anyone in the world who is connected, as long as they have a reasonably standard Web browser: Internet Explorer, Chrome, Safari, Firefox, it doesn’t matter. Everyone can get several browsers, at least, for their computing platform, and so they can access your Web site.

Mobile apps, on the other hand, are gated by the platform owners, specifically Apple and Google; the growth of alternate Android platforms like Cyanogen may help with this, but it is too early to tell with confidence. Apple and Google have been known to be arbitrary and difficult in the past, and opaque as to their reasoning for delays and rejections. While the situation has improved, it is not a stretch to envision a situation wherein Myntra sells clothing that is not illegal in India but is in the United States (where Apple and Google both are based), and their apps are pulled intentionally due to risk management by the companies – what if someone used the Flipkart app to buy ivory while in the United States? – or just a misunderstanding that takes some time to clear up. Could they afford to have their apps disabled, even just for new installs, for a week or two? How about longer?

If Flipkart were a company whose  very existence depended on a local app, like Foursquare or Angry Birds, then the gate is an unavoidable cost of doing business. Without a Web site, however, their entire business is subject to app store owners.

Above and beyond the technical risks, the business risk is not one I would want to take, especially if I were a company that already had an established Web presence.

Summary

Choosing to go mobile first or even mobile only makes sense in many cases.

Shuttering an existing Web site in favour of mobile apps, even when the Web site has become a smaller portion of the business, creates serious technical risks and very serious business risks.

Before you decide to abandon a technology channel because it is causing you problems or is a smaller part of your business, ask us to evaluate:

  1. What is the real source of the problem?
  2. What technology risks do you accept in your solution?
  3. What business risks will you accept?

The answers may surprise you, they may save you, and they certainly will help you grow safely.

About Avi Deitcher

Avi Deitcher is a technology business consultant who lives to dramatically improve fast-moving and fast-growing companies. He writes regularly on this blog, and can be reached via Facebook, Twitter and avi@atomicinc.com.
This entry was posted in business, cloud, product, technology and tagged , , , , , , , . Bookmark the permalink.