About Crafter's Lab
Build your studio. Keep your craft.
Crafter's Lab is my living workshop for solo founders and developers learning to build and operate their own AI-native app studios.
We build real products, explore what agents can take on, and develop the knowledge, skills, and workflows that make the next piece of work easier. Not just another app generated from a prompt, but a way of working that becomes more capable as we do.
You bring your own projects and ambition. I share the product work, systems, experiments, and lessons from my studio. Together with the crew, you learn what to adopt, what to change, and what belongs in the studio you're building for yourself.
Why I Built This
Building solo gives you freedom. It also puts the whole operation on your shoulders.
You choose the product, make the design decisions, build it, check it, explain it, launch it, and figure out what customers need next. Somewhere in between, you're supposed to keep learning, organize what you know, and avoid losing the thread across all the work you've started.
AI changes what one person can do. But a growing collection of tools doesn't automatically become a working studio. You can generate more code and still spend your day repeating context, directing every task, moving information around, and trying to understand whether anything actually worked.
For years, I bounced between generic Slacks, noisy newsletters, and communities that felt more like ad feeds than workshops. I wanted somewhere closer to the work: the decisions, the systems, the experiments that failed, and the things that became useful enough to keep.
Crafter's Lab started from my own need to organize that work. My Notion workspace held builds, documentation, failed launches, prompt libraries, and AI-agent experiments. Opening up useful parts of that practice became a way to share more than a finished result (the thinking and the working systems behind it).
That's still the reason for the Lab. But the ambition goes further now. I want this to be a place where we learn to build the system behind our products, rather than remain the person holding every step together.
The Studio We're Learning to Build
An app is one output. Your studio is the capability behind it.
It's how you decide what deserves to exist, turn that decision into a product, bring it to customers, and keep improving it. It includes your engineering and design practice, but also your agents, accumulated knowledge, reusable skills, workflows, and the way you run the business.
I believe we're moving from asking AI to help with individual tasks toward building systems that can carry meaningful work on our behalf. The opportunity for a solo founder isn't only to build faster. It's to develop capacity that used to require personally doing or coordinating every step.
That capacity takes work to build. Agents need useful responsibilities, the right context, and tools they can actually operate. Predictable steps often belong in code rather than another model conversation. Results need checks that tell us something real. And when a workflow fails, we need to understand where it failed and how to recover.
The founder's role changes, too. You increasingly direct outcomes and improve how work gets done, while staying close to the decisions that need your judgment. You don't have to inspect every detail of every familiar task. But you do need the ability to look closer when something is unfamiliar, the evidence is weak, or the product deserves more care.
That's the studio-building capability we're developing here: a system you can understand, operate, adapt, and improve, not a stack you copy once and hope keeps working.
Learn From the Work Behind Crafter Apps
Crafter Apps is where I build customer products and develop the working system behind them. Crafter's Lab is the workshop where I share useful parts of that practice so you can learn from them.
The software factory behind those products is more than a coding agent. It's the connection between product decisions, knowledge, specialist responsibilities, execution, verification, and feedback. The interesting part is how those connections help real work get done, and which ones turn out to need changing.
In the Lab, we look at the choices as well as the results. Why use an agent for this responsibility? What context does it need? Which steps should be ordinary software? How do we know the result is useful? What happens when it gets something wrong?
You can follow that learning through practical resources, conversations in the Slack Office, and the shared Notion systems included in your membership. Bring your own work into the conversation, compare approaches with other Crafters, and adapt what fits.
The goal isn't to reproduce my entire setup. Your products, constraints, and strengths will be different. The useful thing to take away is the understanding to build a studio that works for you.
What We Learn Here
The Lab connects the responsibilities of a solo studio rather than treating each tool as a separate world.
Build with AI. Learn to give coding tools useful context, design dependable ways of working, and turn understood practice into reusable skills. Get beyond restarting the same conversation for every change.
Build and operate agents. Learn how to give agents meaningful responsibilities, choose where they run, connect them to tools and knowledge, and keep their work understandable over time.
Build Apple products. Develop real product and engineering craft: behavior, design, data, privacy, accessibility, and performance. AI can help with the work; the experience still needs care.
Run the solo studio. Connect projects, knowledge, decisions, and recurring work so you can see what matters and keep moving without carrying the whole business in your head.
Market your products. Learn to explain the value, create useful launch material, reach people, and learn from their response. A capable studio needs a connection to customers, not just a pipeline for producing software.
These are connected paths, not a compulsory sequence. Start with the problem in front of you. The larger understanding develops as you build.
Why Crafter?
"Crafter" is more than a name to me. It describes how I want to approach the work.
A Crafter experiments, learns, changes direction, and cares about what they make. They enjoy the process, but they also want the result to deserve a place in someone's life. They can move quickly without treating every rough edge as somebody else's problem.
That's why the word connects Crafter's Lab, Crafter Apps, and Solo Swift Crafter. The products and activities are different, but the attitude carries through: build things that matter, understand your choices, and keep getting better at the work.
AI doesn't make that attitude less important. When generating something becomes easier, choosing well and finishing with care matter more.
Building a reusable workflow is craft. So is giving an agent a clear responsibility, designing a check that catches a real problem, or removing machinery that creates more work than it saves. Craft isn't measured by how much you do by hand.
And it isn't reserved for a particular title. You can be a developer, a founder, an indie builder, or someone growing into those responsibilities. What matters here is that you're willing to do real work, learn from it, and take responsibility for what you put into the world.
My Mission
My mission is to help solo builders become more capable without losing their authorship, judgment, or enjoyment of the work.
I want the Lab to make ambitious studio-building feel concrete. Not through promises that an agent will run your business, but through practical understanding: how to build a useful capability, see whether it holds up, improve it, and connect it to the rest of your work.
The direction is inspired in part by IndyDevDan's work on agentic operating levels and software factories: where to focus your attention, and how agents and code can combine into reusable systems. Here, we adapt those ideas to the whole solo app studio and learn through our own product work.
I also want this to remain a place with people in it. A good system can reduce repetitive work. It doesn't replace the value of asking a question, comparing an approach, sharing a frustrating result, or having someone notice the progress you've made.
Less noise. More useful practice. More room to make things your way, and a crew to build alongside.
Who's Behind the Lab?
Hey, I'm Daniel, known online as Solo Swift Crafter.
I've spent ten years in the iOS trenches: building apps, freelancing for startups, launching my own products, and learning what it takes to turn an idea into something people can actually use. Swift and Apple development are where I developed my craft, with a designer's eye for how a product looks, feels, and works.
I share that work on YouTube, where 8.2K subscribers follow the builds, deep dives, and experiments, and on Instagram, with 14.2K followers. These are places to see the work behind the Lab and get to know how I approach building, not just read the finished explanation here.
Today, I'm applying that experience to a bigger question: how far can one founder go with a well-built AI-native studio? Through Crafter Apps, I'm building products while developing the agents, knowledge, skills, and workflows that support the work. The ambition is to make the studio more capable without making the products less thoughtful.
Crafter's Lab is where I bring that practice into the conversation. The teaching starts with real work and the judgment behind it: what I tried, what held up, what failed, and what I'm changing. My Apple-development background remains part of that foundation, but the studio we're learning to build reaches beyond writing code.
If you want to get to know me before joining, watch a build, explore a deep dive, or follow along on Instagram. You'll get a clearer sense of the person (and the practice) behind this workshop.
Why a Crafter Code?
Every good crew needs a code. Ours is about how we work and how we treat one another.
Be honest about what happened. Share useful context. Respect other people's work. Ask when you don't understand. Don't present a convincing output as proof that a system works.
We care about products that are Simple, Lovable, Complete: focused on a real need, cared for in the experience, and finished well enough to fulfill the promise, including the awkward edges.
We welcome leverage. Remove unnecessary steps. Let agents and software carry work they can do dependably. But don't confuse generating more with making something better, or delegation with giving up responsibility.
This isn't a place to compete over who has the biggest agent roster or the most impressive automation. It's a workshop for making useful things and becoming better at building them.
Bring your ambition. Bring the messy draft. Bring what you learned when the first attempt didn't work. That's material we can work with.
For Collaborators
I'm open to collaborations that help solo builders develop real capability: a useful guest resource, an honest tool experiment, a practical walkthrough, or a perspective that makes us rethink how we build.
The fit matters more than the format. If your work helps people create better products or operate their studios more thoughtfully, I'd like to hear about it.
Bring Your Work to the Lab
You don't need a complete studio before you join. Bring a real project, a question worth working through, and the willingness to learn by doing.
We're here to build useful products, and the systems that help us keep building them.