Gunjan Karun


Using my 20+ years of experience in building products for startups to build where I help app makers plan their apps better.
Joined November 2022

On Chrome, Tab Groups help.

I spend some time once a while cleaning by tabs.

Here is my cleaning process

Usually, my tabs are there either because I am researching for a specific project/topic or I am just learning/watching/reading stuff.

I close any tab that has been open for more than a few days without me looking at it. Before closing the tab, I ensure I have saved that information.

  1. If the tab is related to a project, I usually have project notes in "Joplin". I copy that URL and Title in the appropriate project notes and close the tab.

  2. If the URL is some reading material, I send that URL to "Pocket" to read later.

  3. If the URL is a Youtube video, I save it to "Watch later" and close it.

  4. If Netflix, add that movie/series to my watchlist and close the tab, and so on.

Please understand that each tab that you have open is very important to you. You are not closing it because you fear losing all the information.

Try to figure out the purpose of these tabs. Save that information somewhere so that you can get it whenever you need it in the future.

Then closing the tab becomes less stressful.

First of all, congratulations on shipping out so many ideas. The mere fact that you shipped it out and somebody is using it is inspiring.

I have many ideas that have never seen the light of day (One such dead project which is used by 7 people in the world is called the

The problem with makers like us is that it is easier for us to start building than actually figuring out whether the app that we are building is worth building or not. In the process, we discount our time and effort and lose the "Opportunity cost". This, in my opinion, is a real and tangible loss that should always be considered before starting any serious endeavor.

I really like your new idea of bots to assist with various tasks. The state of AI is such that you should be able to automate many tasks that needed Mechanical Turks in the past.

The fact that you already have a potential user is the best reason why you must focus on this idea and wow that user. The e-commerce market is also huge so there is great potential for you there.

For how to not get overwhelmed with tasks @marc has already shared some great ideas.
My three tips for that would be
* Make a list of tasks (Todos)
* Decide when and for how long you plan to work on each of those tasks (Time Boxing)
* At the scheduled time, work in chunks of 25 minutes followed by a short break (Pomodoro)
* Do not ignore your physical, mental, and social health in the process. They are of equal importance, if not more important than any idea or product you build.

Best of luck with your app. I would love to be of any help whenever you need it.

Thanks, @marc, for pointing this out.

Let me explain the problem I am trying to solve (maybe you can confirm if the problem is real or not).

When you have a product idea, you must work on two aspects BEFORE the building of the product starts.

First, you need to be very sure of WHAT you are building i.e.
* what problems are you solving,
* is that problem worth solving,
* what do your users feel about that problem,
* come up with some suggestions for a solution,
* engage your users and get their feedback on the problems and solution
The priority here is to find a handful of users with the problem you plan to solve and then keep them involved during the product planning and building phases.

The second part is HOW you solve it. It involves
* Prioritizing the features
* Planning an MVP
* Figuring out how much and how long will the proposed solution take
* Creating a user flow of the recommended features
* Plan the screens and screen flow for each user type
* Creating the UX of your solution
* and so on.

The last part is building the product, which is easy if you take care of the first two parts of planning.

A solution that I have in mind addresses the first two parts of planning using a combination of

  • Technology: A system where users plan the features, collect feedback, create user flows, plan the screens, use a mood board for UI/UX inspirations, and so on.

  • Community: Where the (potential) users of their app can vote/discuss these features/screens/releases etc.

  • Marketplace: Where experts can be hired for specific tasks like creating UIs, Logos, Wireframes, and so on.

Right now, I am still in the exploration phase.

I am conducting a series of in-person meetups in my city, talking to all the startups and people with ideas and figuring out what is essential for them.

BTW, @hailcaesar best of luck. I will continue the discussion in your thread.

The process you describe sounds theoretically correct, although practically I skip most of these steps as a solo founder.

The goal in an early-stage product should be to get as many useful insights as possible. What the market wants, whether you can reach your customer, if you can technically build what you envision, etc.

This means that if you do your job right, you'll keep getting more information that will guide you forward. That means that whatever you plan quickly becomes outdated. You don't want to execute on old ideas that didn't take into account the new insights.

For that reason I find planning more than a few weeks in advance not that useful.

Additional, as a developer, I prefer to build an MVP as quickly as possible to see what resonates with the market. Rather than doing a ton of research which is time consuming and something I simply don't enjoy as much.

I expect that for companies with (larger) teams the steps you outline become a lot more important though. So I think it all comes down to who your target market is.

I suggest that you do A/B tests for all your options and see which option gives you best engagement/least annoyance to your users.

Thanks Gunjan, I'm a big fan of A/B testing, I consider it Guessing Vs Science. But this has nothing to do with data but about business ethics.

What things to keep in mind while planning your app? Features, UI, user flow, user experience, metrics to track, pre-launch tasks, and so on.
Things that we should do BEFORE we start building our app.

Based on my two decades of doing this, I would strongly recommend NOT quit your job at this stage when there is more than a 90% probability that you will fail.

Here are my recommendations
* Spend some time identifying a problem worth solving.
* Find out people who have those problems
* Talk to those people and understand the problem better and how much they are already spending to address that problem
* Plan out how you will address it better.
* Inform them that you are building a solution for them, walk them through your proposed solution, and get their feedback
* If possible, take some advance payment from them (This is optional but try to get some level of commitment from them)

Till that time, I strongly suggest that you do not quit your job.

Finding a good product to build along with users is a time-consuming process. A regular cash flow gives you the freedom of being patient and not make desperate decisions.

This will not be easy. You will have to work extra hours over your scheduled work hours, work on weekends, skip binge-watching Game of Thrones, and so on but this will be a less painful way to build a sustainable startup.

I am active on Reddit, LinkedIn and offline network of startups in my city.

This is how I handle it.

  1. Make a list of todos AND use your calendar app to allocate how, when and for how long will you will work on it. This WHEN is important.

  2. Set alarms for that "when". I set the most irritating alarm on my mobile.

  3. When the alarm rings, I start a timer for 25 minutes.

  4. During the 25 minutes, I force myself to not do anything else. I might not do the intended task but my goal for these 25 minutes is to NOT do anything else. It is either the task or nothing. I am ok with just sitting quietly for 25 minutes, staring at my laptop or the world around me.

  5. Although there are many ways of doing it, I prefer using the Chrome extension for (One of my older apps that I created a few years ago). The Chrome extension is a new tab replacement so every time I open a new tab while surfing Netflix or Reddit, I get to see my entire day in one place :)

This works for me.

I highly recommend "The E-Myth Revisited: Why Most Small Businesses Don't Work and What to Do About It"…

The idea is very simple, just because you bake amazing cakes does not mean that you can run a successful bakery. This book forces you to identify different roles that are needed to make your business successful and then figure out how to onboard, train, and use them.

This book is quite dated but the concepts in this book are still relevant.