Archive

The Dulin Report

Browsable archive from the WordPress export.

Results (89)

Strategic activity mapping for software architects May 25, 2025 On the role of Distinguished Engineer and CTO Mindset Apr 27, 2025 The future is bright Mar 30, 2025 2024 Reflections Dec 31, 2024 My giant follows me wherever I go Sep 20, 2024 The day I became an architect Sep 11, 2024 Are developer jobs truly in decline? Jun 29, 2024 Leadership is About "We," Not "I" Jun 9, 2024 Form follows fiasco Mar 31, 2024 Software Engineering is here to stay Mar 3, 2024 Some thoughts on recent RTO announcements Jun 22, 2023 On Amazon Prime Video’s move to a monolith May 14, 2023 One size does not fit all: neither cloud nor on-prem Apr 10, 2023 Some thoughts on the latest LastPass fiasco Mar 5, 2023 Comparing AWS SQS, SNS, and Kinesis: A Technical Breakdown for Enterprise Developers Feb 11, 2023 Working from home works as well as any distributed team Nov 25, 2022 Why you should question the “database per service” pattern Oct 5, 2022 Book review: Clojure for the Brave and True Oct 2, 2022 Stop Shakespearizing Sep 16, 2022 Why don’t they tell you that in the instructions? Aug 31, 2022 Monolithic repository vs a monolith Aug 23, 2022 Automation and coding tools for pet projects on the Apple hardware May 28, 2022 There is no such thing as one grand unified full-stack programming language May 27, 2022 Most terrifying professional artifact May 14, 2022 If you haven’t done it already, get yourself a Raspberry Pi and install Linux on it May 9, 2022 Good idea fairy strikes when you least expect it May 2, 2022 Kitchen table conversations Nov 7, 2021 Application developers like to think their app is the only one Apr 5, 2021 A year of COVID taught us all how to work remotely Feb 10, 2021 What programming language to use for a brand new project? Feb 18, 2020 The religion of JavaScript Nov 26, 2018 Teleportation can corrupt your data Sep 29, 2018 Let’s talk cloud neutrality Sep 17, 2018 What does a Chief Software Architect do? Jun 23, 2018 Nobody wants your app Aug 2, 2017 TypeScript starts where JavaScript leaves off Aug 2, 2017 Singletons in TypeScript Jul 16, 2017 Emails, politics, and common sense Jan 14, 2017 Online grocers have an additional burden to be reliable Jan 5, 2017 Collaborative work in the cloud: what I learned teaching my daughter how to code Dec 10, 2016 Apple’s recent announcements have been underwhelming Oct 29, 2016 What I learned from using Amazon Alexa for a month Sep 7, 2016 Why I switched to Android and Google Project Fi and why should you Aug 28, 2016 Amazon Alexa is eating the retailers alive Jun 22, 2016 In search for the mythical neutrality among top-tier public cloud providers Jun 18, 2016 In Support Of Gary Johnson Jun 13, 2016 Files and folders: apps vs documents May 26, 2016 What can we learn from the last week's salesforce.com outage ? May 15, 2016 Why it makes perfect sense for Dropbox to leave AWS May 7, 2016 JEE in the cloud era: building application servers Apr 22, 2016 Let's stop letting tools get in the way of results Apr 10, 2016 JavaScript as the language of the cloud Feb 20, 2016 LinkedIn needs a reset Feb 13, 2016 In memory of Ed Yourdon Jan 23, 2016 Our civilization has a single point of failure Dec 16, 2015 IT departments must transform in the face of the cloud revolution Nov 9, 2015 I Stand With Ahmed Sep 19, 2015 Setting Up Cross-Region Replication of AWS RDS for PostgreSQL Sep 12, 2015 Top Ten Differences Between ActiveMQ and Amazon SQS Sep 5, 2015 We Live in a Mobile Device Notification Hell Aug 22, 2015 What Every College Computer Science Freshman Should Know Aug 14, 2015 On Maintaining Personal Brand as a Software Engineer Aug 2, 2015 The Three Myths About JavaScript Simplicity Jul 10, 2015 Book Review: "Shop Class As Soulcraft" By Matthew B. Crawford Jul 5, 2015 Attracting STEM Graduates to Traditional Enterprise IT Jul 4, 2015 Your IT Department's Kodak Moment Jun 17, 2015 The longer the chain of responsibility the less likely there is anyone in the hierarchy who can actually accept it Jun 7, 2015 Big Data is not all about Hadoop May 30, 2015 Smart IT Departments Own Their Business API and Take Ownership of Data Governance May 13, 2015 The Clarkson School Class of 2015 Commencement speech May 5, 2015 Why I am not Getting an Apple Watch For Now: Or Ever Apr 26, 2015 My Brief Affair With Android Apr 25, 2015 Exploration of the Software Engineering as a Profession Apr 8, 2015 What can Evernote Teach Us About Enterprise App Architecture Apr 2, 2015 Microsoft and Apple Have Everything to Lose if Chromebooks Succeed Mar 31, 2015 Do not apply data science methods without understanding them Mar 25, 2015 On apprenticeship Feb 13, 2015 On Managing Stress, Multitasking and Other New Year's Resolutions Jan 1, 2015 Why I am Tempted to Replace Cassandra With DynamoDB Nov 13, 2014 Software Engineering and Domain Area Expertise Nov 7, 2014 Docker can fundamentally change how you think of server deployments Aug 26, 2014 Wall St. wakes up to underinvestment in OMS Aug 21, 2014 Software Engineers Are Not Doctors Aug 3, 2014 Thanking MIT Scratch Sep 14, 2013 Have computers become too complicated for teaching ? Jan 1, 2013 Thoughts on Wall Street Technology Aug 11, 2012 Scripting News: After X years programming Jun 5, 2012 Java, Linux and UNIX: How much things have progressed Dec 7, 2010 Eminence Grise: A trusted advisor May 13, 2009

Nobody wants your app

August 2, 2017

You have a product. You have a service. You have a business plan. Now you want to leverage technology and build a relationship with your customers by offering them an app. I am here to talk you out of it.



Nobody wants an app



You may feel like you are extending your brand to your customers' smartphones by giving them an app. In reality, however, it is a false sense of security.



The concept of an app to install has been around ever since computers with permanent disk drives became widely available to consumers, i.e. the early 1990s. Things became a bit more convenient lately with the rise of App Stores and mobile payments. The fundamentals of the process have not changed – a brand, or a company, ask that you download an app and install it on your computer and use it.



Remember back in the 1990s when a “PC Magazine” issue would come with a CD with “free software” on it? It would have all sort of junk on it that brands wanted you to have on your computer. In that regard, little has changed except now brands want to occupy memory on your smartphone and track your every movement.



Asking people to install an app is just a way of creating barriers for people to start interacting with your brand. The reality is that nobody wants another app on their phone. What your customers want instead is a path of least resistance to getting something done – purchasing a product, booking a service, or contacting you.



There is something else that both you and your customers want – a relationship. Consumers aren't just looking for a service provider – they are looking for a trusted advisor. Both you and your customers will benefit from this long term relationship.



The path of least resistance



Building an app requires UX design, front end and back end coding, App Store approval process, and a never ending maintenance cycle. Most apps on the Apple App Store have meager retention rate. People install an app and then never use it.



On the other hand, there is a channel for reaching your customers that is not going away: messaging. To get straight to the point – you shouldn't build an app, you should make a chat bot.



In some ways, a chat bot is easier to develop than an app. You skip the whole process of UX design and front end development. You just focus on the interactions and the back end development. If you do it right, the back end can be reused for other forms of applications later. A chat bot, in other words, lets you reach your customers faster and cheaper.



Intelligent agent



Imagine a chat bot that is also an intelligent agent. Here is what I mean by that.



From the customer's perspective, an AI-backed chat bot delivers a truly personalized experience. It notifies the user of products and services that they might be interested in – based on what the agent learned about them.



From the customer's perspective what they perceive is a “robo-advisor” that is there for them permanently, from day one, to offer insight and advice uniquely suited just for them. It is as if this chat bot's only reason for existence is to make your customer's life better.



Some final thoughts



Regardless of whether you are planning an app or a chat bot, don't forget that there are three main dimensions to any business application:




  1. Your customer and how they interact with your brand,

  2. Your employees and how they deliver goods and services to your customers, and

  3. You, as a business owner, who needs a dashboard and key performance indicators to have insight into how your business is performing



You could accomplish all three with a chat bot, but that may not be appropriate. If I were architecting an app ecosystem for a brand, I would make a chat bot for the consumer and for the employees, but have an app for the business owner. I would evolve all three at the same time.



I wish I had concrete evidence or statistics to prove my point. You can google around and find articles out there on this topic, but for this post, I just wanted to get something out of my head.