About Natsu Labs

An independent studio building practical software.

Natsu Labs is Kurt Diano's independent software studio. Current work spans learning tools, instructor workflows, Android apps, websites, and business systems.

Why it exists

One home for products, client work, and engineering.

Natsu Labs gives Kurt's software work one clear home instead of treating every project as an isolated portfolio piece. It is where active products can grow, client work can be presented responsibly, and useful experiments can stay discoverable without competing with the strongest work.

The studio is still growing. The priority is to build useful software, keep the work understandable, and improve products through real use.

What Natsu Labs builds

Products first, with focused client and engineering work.

Current work stays focused on problems Kurt can design, build, test, and support directly.

Client & practical work

Websites, apps, systems

Focused websites, Android applications, business systems, MVPs, and existing-product improvements where the scope is clear enough for direct ownership.

Supporting engineering

Experiments that still teach something

Echo, Prima POS, PixSense, Memora, Palli, and earlier work remain part of the studio history when they demonstrate a useful technical or product lesson.

How the work is approached

Start with the real workflow.

Good-looking software still fails when the underlying workflow, state, or recovery path is weak. Natsu Labs puts those details into the product work early.

  1. Start with what the user is trying to finish.

    Map the real action, the information it needs, and where the workflow can fail before adding more screens.

  2. Build a coherent first release.

    Prefer a smaller version that completes the core job over a large feature list with weak connections between parts.

  3. Treat reliability as product work.

    Saving, recovery, validation, mismatch handling, performance, and failure states are part of the experience—not cleanup after the interface is done.

  4. Keep communication close to implementation.

    Scope, tradeoffs, limitations, and changes are easier to discuss when the person planning the work is also involved in building and testing it.

Kurt Diano, founder of Natsu Labs
Teaching stays close to the work

Teaching keeps real learning problems close to the products.

Kurt also works as an IT Instructor. That keeps beginner questions, classroom routines, debugging explanations, and the friction of everyday teaching close to the software he builds.

Kodari grows from the need to make Android concepts easier to try. Acadence grows from the need to manage instructor work without scattering attendance, records, students, and follow-up across disconnected tools.

Open Kurt's developer portfolio
Current direction

Grow from products people can actually use.

NowKodari

Public beta preparation and reliability/performance hardening.

NowAcadence

Faculty pilot preparation around real instructor workflows.

NextAndroid publishing

Prepare the publishing foundation for future Google Play releases as real apps reach release readiness.

Explore or work together

Explore the work or bring a project.

Use the portfolio to inspect the engineering, try Kodari if you are here as a user, or send the current workflow or project idea if you are considering working with Natsu Labs.