How we make

Build small. Use it yourself. Share what you learn.

We start with a frustration, build a small app and prepare it for release. Lessons from use and feedback become a record for the next attempt.

Six-step loop

One frustration. Six steps. A new starting point.

The sequence helps us avoid rushing. What we learn from actual use brings us back to the beginning.

  1. Notice a frustration

    Observe an everyday task that repeats or feels cumbersome. Describe the problem in one sentence.

  2. Build a small app

    Choose a small scope that solves the most important part first, and make something you can try.

  3. Release and use

    Verify a safe official distribution channel. Start by using the app in your own everyday life.

  4. Listen to users

    Listen for bugs, usability difficulties and ideas, and collect concrete opportunities for change.

  5. Update and improve

    Understand the context, set priorities and make small updates. Use the app again to check the result.

  6. Share the experience

    Record lessons and unsuccessful attempts so other makers, and your next project, can benefit.

Making rules

Start small. Follow through to everyday use.

The path to actual use and safe release matters more than the size of the idea.

  • Start with one thing

    Choose the smallest scope that eases one frustration, rather than promising a long list of features.

  • Use it for real

    Go beyond a screen that looks good. Try the app in everyday situations and find what still gets in the way.

  • Share a verified official path

    Provide only verified official destinations. Do not distribute installation files or links of uncertain origin.

  • Keep a feedback record

    Record bugs, difficulties, suggestions and the reasoning behind decisions, as well as what went well.

Share back

Share the process as well as the result.

Finished features are only part of the story. Notes can turn practical lessons into a clearer start for someone else.

  • Practical know-how

    Explain how you kept the scope small and which implementation choices others might reuse.

  • Trial and error

    Share approaches that failed, what changed and why, with enough context for others facing the same problem.

  • Development trends

    Look at how new tools and approaches help small projects, rather than simply following what is fashionable.

Keep exploring

Explore the apps and the lessons behind them.

Our apps page introduces the work. Notes will share what we learn from making it.