Codemuse
Anna Lasończyk — software developer and founder of Codemuse studio

Apps & AI solutions

Apps peopleactually want to use

I design apps and AI-powered solutions from the first idea through launch. You get one person accountable for the whole process, modern technology and a product refined down to the details.

Taking on projects
Scroll

What I do

Three things, done properly

/01

Web applications

Sites and platforms that load fast, show up in Google and don't fall apart around the fiftieth screen. From landing pages through customer portals to internal tools you simply can't buy off the shelf.

  • Search-friendly sites
  • Client portals & dashboards
  • Internal tooling
  • System integrations
/02

Mobile applications

One app that works on iPhone and Android — with a native feel, push notifications, offline support and updates that ship without waiting on the store review queue.

  • iOS and Android from one codebase
  • App Store & Google Play releases
  • Offline mode and notifications
  • Updates without resubmission
/03

Products from scratch

You have an idea, but not a finished specification. I help select the features that matter, use AI where it creates real value and get the first version into users' hands quickly — without wasting budget on extras.

  • Scoping workshop and estimate
  • MVP ready to test
  • AI features and automation
  • Post-launch support
Anna Lasończyk — software developer and founder of Codemuse studio

About

Anna Lasończyk

Developer · founder of Codemuse

I've been building software commercially for several years — usually the kind somebody actually works in every day: operational dashboards, team apps, products that have to survive contact with real users.

I combine product thinking with software development and work with AI tools every day. I use them both to build intelligent product features and to prototype and deliver projects more efficiently.

I do my best work on projects where craft matters, not just ticking features off a list.

Languages
Polish, English
Engagements
Project, MVP, ongoing retainer
Web applications|Mobile applications|iOS & Android|Dashboards & admin panels|Integrations & APIs|AI features & automation|MVP in weeks|Web applications|Mobile applications|iOS & Android|Dashboards & admin panels|Integrations & APIs|AI features & automation|MVP in weeks|

Toolkit

What it's built with

I pick tools to fit the problem, not the other way round. Day to day, this is the set:

Front

  • React
  • Next.js
  • TypeScript
  • Tailwind CSS

Mobile

  • React Native
  • Expo
  • EAS Build

Backend

  • Node.js
  • NestJS
  • PostgreSQL
  • REST & GraphQL

Process

Four steps, no surprises

01

Conversation

An hour on what needs to happen and for whom. You leave with an honest opinion, even if we never work together.

02

Scope & estimate

A concrete document: what gets built, in what order, how long it takes and what it costs. No six-month ranges.

03

Build

Short cycles and a clickable version from the first weeks. You always know where things stand without asking for a status update.

04

Launch & care

Release, monitoring, fixes. You get the code, the access and the documentation — you're never locked in.

FAQ

Before you write

The budget depends mainly on scope: how many features and integrations are involved, and how complete the product needs to be at launch. After our first conversation I put together a firm quote with a timeline — usually within a few days.

Contact

Tell me what you're building

Two sentences on what it is and when you need it. I reply within one business day — including when I think I'm not the right person for the job.