Skip to main content

App-pocalypse

Have you recently tried to shop on any Indian e-commerce website? If you have, you too would be frustrated by the constant nagging done by these sites to download their app. Myntra has gone ahead and shut its website down completely! Others like Flipkart won't let you browse any product in peace and will immediately try to "connect" you to their app - even when you are already at their site and trying to buy a product. Amazon India will release "app-only" offers and discounts.


All this is done in the garb of making customer experience better.


Only problem is that it makes user experience even worse. These companies are trying to lure the consumer into a walled garden so that they make bad, misinformed buying decisions. Let me elaborate.

On a desktop browser, you can easily search for and compare products across various websites with just a few tabs open. You don't need to switch context and lose track of what you were trying to compare when you move to a different product.

On a mobile screen, only one product is visible at a time. Even with only one product visible, you cannot see all the information about that product on one screen - reviews, ratings, QnAs. To read each review or product detail, the screen changes constantly leaving the consumer totally clueless.

I understand the monetary benefits of maintaining only an app with reduced IT, development and maintenance costs. But that should not come at the cost of user experience. 

Apps should exist as a choice. These companies should stop trying to make them the only option and need to actually follow up on their mantra to let consumers "shop anywhere, anytime".

As XKCD has put it very correctly, Flipkart, Amazon IN and others, if you are reading this please just stop. 


Comments

Popular posts from this blog

Integrating React with SonarQube using Azure DevOps Pipelines

In the world of automation, code quality is of paramount importance. SonarQube and Azure DevOps are two tools which solve this problem in a continuous and automated way. They play well for a majority of languages and frameworks. However, to make the integration work for React applications still remains a challenge. In this post we will explore how we can integrate a React application to SonarQube using Azure DevOps pipelines to continuously build and assess code quality. Creating the React Application Let's start at the beginning. We will use npx to create a Typescript based React app. Why Typescript? I find it easier to work and more maintainable owing to its strongly-typed behavior. You can very well follow this guide for jsx based applications too. We will use the fantastic Create-React-App (CRA) tool to create a React application called ' sonar-azuredevops-app '. > npx create-react-app sonar-azuredevops-app --template typescript Once the project creation is done, we

Creating a Smart Playlist

A few days earlier I was thinking that wouldn't it be nice if I had something which will automatically generate a playlist for me with no artists repeated. Also, it would be nice if I could block those artists which I really hate (like Himesh Reshammiya!). Since I couldn't find anything already available, I decided to code it myself. Here is the outcome -  This application is created entirely in .NET Framework 4/WPF and uses Windows Media Player Library as its source of information. So you have to keep your Windows Media Player Library updated for this to work. It is tested only on Windows 7/Vista. You can download it from here . UPDATE : You can download the Windows XP version of the application here . Please provide your feedback!

Add Git Commit Hash and Build Number to a Static React Website using Azure DevOps

While working on a React based static website recently, there was a need to see exactly what was deployed in the Dev/Test environments to reduce confusion amongst teams. I wanted to show something like this: A quick look at the site's footer should show the Git Commit Hash and Build Number which was deployed and click through to actual commits and build results. Let's see how we achieved this using Azure DevOps. Git Commit Hash Azure DevOps exposes a variable called  $(Build.SourceVersion) which contains the hash of the commit. So I defined a variable in the Build Pipeline using it. Build Id and Build Number Azure DevOps also exposes two release time variables  $(Build.BuildId) and  $(Build.BuildNumber) which can be used to define custom variables in the pipeline. So we have a total of 3 variables defined: Next we use these variables in our React App. I created 3 global variables in index.html and assigned a token value to them. < script   type = "text/JavaScript&quo