Skip to main content

So you want to start a mobile app business...

I wrote this letter to a friend of mine who was looking for a technical co-founder for a mobile-first
startup.  I figured it might be a good idea to share this with my readers (after a bit of cleaning up).

Letter to Chris:

Hey man!  I am glad you got your entrepreneurial juices flowing.  So here is what I can tell you about exploring your idea further.

First of all there are a lot of ideas floating around and a bunch of people are building apps, however there are very few *good* ideas.  I trust that you have a good idea because I know you are a smart guy.

How do you prove to people that it's a good idea?  Actually building stuff is just a part of the equation.  Getting it connected to customers is the bigger part.  Think about it as if you were looking for oil.  Imagine you approach an engineer and say, "I need to drill for oil!" Drilling for oil is useful but where and how much oil is there is the bigger question.

How does this relate to your business?  First thing first - get in touch with people who would use it and buy it.  If you can't find those people, guess what - there ain't no oil there!

When you find those people the next question is: what's your plan for monetization?  Is it ad-supported, is it supported by people paying for a premium version or something else?

I don't know much about ad-supported things.  Those generally compete for your attention and there is a fair amount of psychology that goes into that, however, let's go with the app that people actually want to pay for.  In this case it's a little simpler to figure out if there is oil and how much oil there is.  Again get back to your potential customers and see what they think.  If you can't find 5-10 people who will spend time talking to you about it and then at the end won't say: "yeah I'd give you some cash for that," again, “the oil field” isn't that big and it might be time to go back to the drawing board.

Pro tip: when you talk to your potential customers you can grab software online that will sketch the app for you.  It's not going to do anything functionally; it will just be screens with outlines.  You can use or FluidUI for almost no money to just create a few screens.  Run them by the your potential customers, you will be surprised how much additional feedback you will get from just giving them something to look at.

So now you are thinking - "WTH!  I need to spend all this time to just get a basic app running, and I don't even have an app.  That's too long and boring!"  Actually what you did do there is some really good market research.  At the end of the exercise you will have (a) a few people to beta test the app, (b) maybe even a couple that will help you fund the development and (c) a sketch of what you want that's been vetted by your early adopters.  This is a well-defined idea and at that point you are actually an entrepreneur with a definite plan.


Popular posts from this blog

SDET / QA Engineer Interview Checklist

After interviewing and hiring hundreds of engineers over the past 12+  years I have come up with a few checklists.  I wanted to share one of those with you so you could conduct comprehensive interviews of QA Engineers for your team.

I use this checklist when I review incoming resumes and during the interview.  It keeps me from missing areas that ensure a good team and technology fit.  I hope you make good use of them.  If you think there are good questions or topics that I have missed - get in touch with me!

SDE/T or QA Engineer interview checklist from Mike Borozdin
If you like this checklist you might want to check out these posts:
Emotional Intelligence in Software Teams  and Good-bye manual tester, hello crowdsourcing!

Code versus Configuration

At Ethos we are building a distributed mortgage origination system and in mortgage there is a lot of
different user types with processes that vary depending on geography.  One of our ongoing discussions is about how much of the logic resides in code vs. being in a workflow system or configuration.  After researching this topic for a bit, I have arrived at a conclusion that the logic should live outside of code very infrequently, which might come as a surprise to a lot of enterprise software engineers.

Costs of configuration files and workflow engines First thing that I assume is true is that having any logic outside of the code has costs associated with it.  Debugging highly configurable system involves not only getting the appropriate branch from source control, you also need to make sure that the right configuration values or the database.  In most cases this is harder for programmers to deal with.  In many FinTech companies where the production data is not made readily accessible…

Should this be a microservice?

After having developed several distributed systems and been a part of dozens of architectural discussions I decided to put together a way to frame the microservices debate. Microservices have been fashionable for some time. A lot of it stemmed from the fact that big and successful cloud companies are using microservices.  It seems reasonable that to create a “serious system” one must be using serious tools and architecture, today it’s microservices.  No engineer wants to be called out for creating a solution that “doesn’t scale.”

The definition for a microservice varies, but overall it tends to be a piece of your system that can run somewhat independently (unless of course it depends on other microservices) and has a REST or queue processing interface.  Overall code encapsulation and separation of concerns have all been around for a long period of time.  Current evolution with containers, fast networks and REST API allows people to easily integrate pieces of their system using web se…