Practical guide · Updated August 17, 2026
Using AI to build websites, apps and more: my method
How I use two AI models to shape a project, guide development and keep the work focused on what matters.
01 / Start here
Begin with a clear idea of what you want to make.
Before writing code, I size up the project: who is it for, what problem should it solve, and what would make it useful? With AI, I no longer need to understand every nuance of programming to move an idea forward. Creativity matters, but so does being able to explain what I want to build.
When I develop a website or app, I use two models with different roles.
02 / Two roles
One model plans; the other builds.
The first helps shape the project: its structure, purpose and necessary steps. Together, we prepare the instructions and prompts for the model that writes the code. The first model then reviews that work and helps me judge whether it serves the project.
This approach takes attention and can be hard to follow over several days. In return, it gives me a clearer direction and helps catch problems before they pile up.
03 / Stay on course
Keep bringing the conversation back to the goal.
I’ve found I need to remind the task-planning model of the business purpose and project priorities, especially when a conversation stretches over days. Otherwise, prompts can get too focused on small details and lead to additions that do little for the product.
Both models can drift. When they do, I bring them back to the original goal and the few things that matter most. Experience helps here: understanding code, or having built something similar before, makes it easier to tell a real risk from an “what if” that doesn’t need to slow the project down.
For me, this makes AI-assisted development more focused and easier to review, whether I’m working on a website or an iOS or Android app.
Frequently asked questions
What to remember.
Do I need to know how to code to use this method?
Not necessarily to get started. You do need to describe the product, judge priorities and review the results carefully.
Why use two models?
Separating planning from code production gives me room to define tasks and review the work before moving on.
Does this approach make the code secure?
It makes review easier, but it does not guarantee security. Code still needs to be checked and tested for the project.