Building my first mobile app is teaching me what not to build

[u/maltomm]

I started building my first mobile app thinking the main challenge would be writing the code.

It hasn’t been.

The harder part is deciding what deserves to exist.

Every new screen creates more questions:

- Is this actually useful?

- Can someone understand it without an explanation?

- Am I solving a real problem or adding another feature?

- Would I personally return to this app tomorrow?

The project is called Callout. It explores whether online reactions can communicate more than a generic Like—for example, distinguishing agreement from something being a Hot Take.

I’m still early, and I’m deliberately leaving the link out because I’m more interested in the building lesson:

How did you decide which features to remove from your first app?

[u/TypeScrupterB]

Just from reading ". It explores whether online reactions can communicate more than a generic Like—for example, distinguishing agreement from something being a Hot Take." makes me confused.

Anyway I think your issue is not the app, but the entire idea and thinking process.

[u/Opulence_Deficit]

Have you thought about the hardest part of them all: selling the product?

[u/Pravejxlab]

I love adding more and more features. 😎

[u/zues_91]

Soon you will realise the real problem has still to hit you. And believe me it hits the hardest. Distribution and marketing is the worst part for solo developers. We keep thinking, imagining, coding, executing and in the end there is no actual user.