Edon Luta was building MasterOnce around learning to code through practice, play and making things. I shared his invitation to beta testers before the planned App Store launch. The part I liked: you get to try what you are learning.
That invitation belongs to the beta period. For today’s availability, check the app’s own channels. The learning idea is the part I want to carry forward here.
If you are starting to code, choose a small thing whose behaviour you can describe. For example, a button that changes a message, or a list where you can add and remove an item. These are suggested exercises, not claims about the app’s lessons.
Build the simplest version, change one part and observe the result. If it breaks, try to explain the difference between what you expected and what happened. That explanation gives you a more precise question to investigate than “I don’t understand coding”.
The source post describes the app as vibe coded. That phrase captures the enthusiasm around building with AI assistance, but it does not show how much any learner understands. A working result and an explanation of the result are separate checks.
After receiving suggested code, try to explain what each important part does. Change a requirement and see whether you can adapt it. If you cannot yet explain something, that is a useful place to continue learning.
The point of practice is not to avoid theory forever. It is to give the theory a concrete question to answer. Make something small, notice what you do not understand, and return to it with a better question.
If you are choosing where to begin, my note on AI tools and learning foundations separates a first experiment from a course of study.