Building an AI App Is Getting Easier. Letting Someone Use It Should Be, Too.

You've built a small app on your computer. It works with your inputs, does something useful, and feels ready to share.

Then you start writing the instructions for someone else.

Download this. Install that. Open the right tool. Follow these steps.

Before long, the instructions are longer than the description of what the app actually does.

This is a problem we're working on at Taku. Helping someone create an app is only part of the job. That creation also needs a practical way to reach the next person.

Taku brings together app creation, a Marketplace for publishing and discovery, and now Taku Sites: a way to publish compatible apps and skills as interactive web experiences.

In short:

• Build in Taku, or bring a project you've already made in Codex or Claude Code.
• Publish it to Taku Marketplace, and, where compatible, as a Site with its own link.
• Share the link. The person on the other end opens it in their browser and tries it with their own input.

Here's how those pieces fit together.

A useful app can begin with an ordinary frustration

You don't need a startup idea to have a reason to build software.

Maybe you keep copying information between documents. Maybe an existing tool almost fits your routine, but its layout or process gets in the way. Maybe you've saved a workflow someone shared and wish you could adapt it without figuring out the entire setup.

These are good starting points because you already understand the problem. You know what you're trying to do and what makes it inconvenient.

Inside the Taku desktop app, you can describe that need in plain language and ask Taku to turn it into an app.

A starting prompt might be:

"Build a tool that turns my meeting notes into a checklist, with a place to edit the owner and deadline for each task."

You don't have to specify every detail in the first sentence. Once you have something to try, you can respond to it: change the layout, adjust the output, or add something you realize is missing.

That back-and-forth matters. An idea often gets clearer once you can interact with it. You may discover that the feature you thought was essential is unnecessary, or that one small change makes the whole tool more useful.

Taku's build experience is designed around that loop: describe, try, refine. You can also explore existing apps and remix one around your own needs.

A sentence gets the process started. Testing and judgment turn the result into something worth sharing.

Your app can have more than one home

Once you've made something useful, the next question is where it should live.

You might drop a Site link into a social post, send it to a friend, or share it with a community discussing the problem your app solves. Instead of asking people to recreate your setup, you invite them into the experience itself.

The format should follow the creation. Some apps depend on desktop capabilities; others make sense as a browser-based web application. Publishing as a Site depends on compatibility, and some projects may need adjustments first.

Already building in Codex or Claude Code? Start there.

Not everyone needs help getting from an idea to a working project.

Some creators already have apps, skills, and experiments built with Codex or Claude Code. Their next challenge is publishing that work in a form other people can access.

Taku's official Publisher plugins provide that route from inside Codex and Claude Code. To publish Sites, install the standard release, which includes the Sites skill; the separate Publisher-only bundle leaves it out. If you haven't used one before, a plugin is a packaged add-on that brings new commands and skills into your coding agent. Anthropic's plugin documentation explains the format, and our guide to Claude Code plugins covers how people use them day to day.

Through the plugin, you can ask Taku Publisher to prepare and publish an existing creation as a Taku App or, where compatible, a Taku Site.

You keep working in the environment you prefer. You don't need to recreate your project inside Taku to bring it into the ecosystem.

That gives creators two starting points:

1. Build something new in the Taku app.
2. Publish something you've already made through the official plugins.

Both lead to the same place: work that other people can discover and use.

The person trying your app should have less to figure out

From a user's perspective, the most interesting question is usually simple: will this help me do what I need?

A Taku Site lets them answer that in their browser. They open the page, enter their own inputs, and see real results, without installing the Taku desktop app for the web experience.

Their inputs are what make this useful. A demo shows how a tool behaves in a situation the creator picked. Trying it yourself shows whether it works for your situation.

Some Sites ask visitors to sign in with Taku before they run, and some draw on the visitor's own Taku account to do their work. Requirements depend on the app, so browser access doesn't mean every experience is anonymous or free. What Sites removes is the desktop installation step, while giving a compatible creation its own web interface.

For someone who is curious but not yet committed, that is a far more approachable place to begin.

A shared link is the beginning of feedback

Making an app accessible won't automatically make it useful. It does give you a better chance to find out.

Someone else may read your instructions differently. They may enter an input you never considered, or get stuck before reaching the part you spent the most time building.

Those moments tell you what to improve.

For an early creator, the first useful feedback doesn't have to come from a big launch. It can come from a handful of people who actually have the problem you're trying to solve. This is the core idea behind usability testing, and Nielsen Norman Group's research on testing with just five users found that a small group surfaces most of the problems worth fixing.

So give a few people the link and let them attempt the task without explaining every step. Then ask:

• Could they tell what the app was for?
• Did the result make sense?
• What did they have to work around?
• Would they come back to it?

Building got cheap; getting the next person to try your work didn't, which is the gap we wrote about in Building Got Cheap. Distribution Didn't. That's the connection we want to make easier: from creating something for yourself to learning how it works for someone else.

Where Taku is today

Taku is in Beta. We're continuing to improve the build experience, publishing flows, compatibility, and the apps people ultimately interact with. A generated app still needs testing, and a project may need refinement before it's ready to share.

Today, the path we're building around is straightforward:

• Start with an idea: describe it in Taku, create an app, and refine it through use.
• Bring existing work: use the official Taku Publisher plugins in Codex or Claude Code to publish your project.
• Make it accessible: publish to Taku Marketplace and, where compatible, share an interactive Site people can try in their browser.

We want more people to experience the satisfaction of making a small piece of software that fits their needs, and then discovering that it helps someone else, too.

FAQ

What is Taku Sites?

Taku Sites publishes a compatible Taku app or skill as an interactive web page with its own shareable link. People can open it in a browser and try it with their own inputs, without installing the Taku desktop app.

Can I publish an app I built in Claude Code or Codex?

Yes. Taku's official Publisher plugins work inside Claude Code and Codex. You can ask Taku Publisher to prepare an existing project and publish it as a Taku App or, where it's compatible, as a Taku Site.

Does every app work as a Site?

No. Some apps rely on desktop capabilities that a browser can't provide, and some projects need adjustments before they can be published as a Site. Those can still be published to Taku Marketplace.

Do people need a Taku account to use a Site?

It depends on the app. Some Sites ask visitors to sign in with Taku before they run, so browser access doesn't mean every Site is anonymous or free.

---

If there's a tool you've been meaning to make, start building with Taku. Bring the idea. Give it a first version. Then give someone a way to try it. Taku is in Beta, and the Mac app is available now.