Module 1: Course Lessons Native interfaces are how you call platform-specific code from a Codename One application without giving up the portability of the rest of the project. When Codename One says “native” in this context, it does not mean Java’s ordinary native keyword. It means “use the platform’s own language and APIs” when you need something that the portable Codename One layer does not expose directly. ...
Module 6: Miscellaneous Features Preview is one of the most important features in a builder product because it turns editing from abstract configuration into immediate feedback. This lesson finally gives that idea the implementation attention it deserves. The side menu matters here because it helps the builder feel like a complete tool rather than a pile of forms. Small visual decisions such as padding, selection styling, and header content do more than improve aesthetics. They make the product feel stable and intentional while users move between editing contexts. ...
Module 6: Miscellaneous Features About pages are easy to underestimate because they are rarely the headline feature of an app. In practice they matter a lot. They give the product a place for identity, contact information, explanatory content, and other material that should exist without cluttering the main workflow. ...
Module 5: Architecture At some point a project can no longer live as a collection of forms and helper methods. Once the UI starts to stabilize, the next step is to make the data model explicit and decide where application state should live. That shift is what this lesson is about. ...
Module 5: Architecture Once the model exists, the next question is whether the UI is truly using it or just sitting beside it. This lesson is the point where the restaurant, menu, order, and dish data start driving what the application shows instead of merely backing it in theory. ...
Module 7: Style Form Style customization is where the app maker stops being a form editor and starts behaving like a product-design tool. That shift is important, because once users can see and alter the look of the generated app directly, the builder becomes much more compelling. ...
Module 7: Style Form Once the style form exists, the next design problem is deciding how customization should be presented. The popup approach in this lesson is a good answer because it keeps the editing UI close to the thing being edited and limits the choices to what actually makes sense for that element. ...
Module 6: Native Interfaces - Billing Native interfaces are most useful when the Java side stays small, deliberate, and easy to reason about. The mistake developers often make is trying to expose every detail of a native SDK directly into the portable layer. That usually creates a fragile API that mirrors platform quirks instead of hiding them. ...
Module 6: Native Interfaces - Billing Most native integrations fail before the first line of native code ever runs. The usual problem is dependency setup: the Java wrapper may be correct, but the native platform build is missing the SDK, targeting the wrong platform level, or pulling in conflicting configuration. ...
Module 7: Style Form Color and font controls are where a style editor can become either empowering or exhausting. This lesson stays on the right side of that line by keeping the tools practical rather than pretending to be a full professional design suite. The color picker works because it balances directness with precision. Sliders give users a tactile way to explore, while the hex value keeps the result grounded in something explicit and reusable. That combination is usually enough for a product builder. Most users do not need a huge color science interface. They need a reliable way to land on a good color and see it applied immediately. ...