Module 7: Native Interfaces - Camera The last part of the iOS camera work is where the bridge becomes truly useful: still capture, video capture, and the callback path back into the portable layer. Once those are in place, the camera integration stops being a preview widget and becomes a working feature. ...
Module 8: Push and In-App Purchase If HTTP polling is the safety net, WebSockets are the more polished fallback. They preserve the event-driven feel of push without depending on the mobile push infrastructure, which makes them a good fit for workflows like build completion, job status changes, and other lightweight live updates. ...
Module 8: Putting it All Together Finishing an application is usually less about adding one big feature than about making a lot of practical decisions that keep the product moving. This lesson starts that final assembly process by focusing on the network layer and on one of the most important development skills in product work: defining a finish line and refusing to keep expanding it. ...
Module 8: Push and In-App Purchase In-app purchase is one of those features where the code is usually easier than the store setup. Apple and Google own the payment flow, product definitions, pricing, refunds, and approval rules. Your app mostly needs to define what is being sold and decide what to unlock when a purchase succeeds. ...
Module 8: Putting it All Together Order flows are where attractive demos become real products. As soon as delivery is involved, the app needs to collect an address, remember it sensibly, and enforce the business rules that determine whether an order can actually be placed. ...
Module 9: Setting Up a Cloud Server At some point the app has to leave the laptop and run somewhere public. This module takes the deliberately pragmatic route: rent a small VPS, install what the backend needs, and get to a working deployment without pretending that this is a full course on cloud architecture. ...
Module 8: Putting it All Together As the menu grows, navigation becomes as important as presentation. A visually nice screen is not enough if users cannot narrow the list to what they want quickly. That is where category filtering and search start to matter. The search approach in the older lesson is implemented manually even though Codename One has higher-level search toolbar support. That remains a useful teaching example because it exposes the moving parts: toggling the toolbar state, swapping in a text field, listening for changes, and filtering the visible content based on the underlying model. ...
Module 9: Setting Up a Cloud Server Once the server exists, the next job is to make it useful. That means installing the packages the backend depends on, getting the database into a safe enough state for internet exposure, and making sure the application can be reached through the usual HTTP and HTTPS ports. ...
Module 9: Security Security is one of the easiest areas to discuss in slogans and one of the hardest to handle well in real software. The first thing worth saying clearly is that security is always a trade-off problem. Stronger protections often add cost, complexity, or friction. That does not make them optional. It means they have to be applied thoughtfully. ...
Module 9: Setting Up a Cloud Server Manual deployment is tolerable exactly once. After that, you want a repeatable way to copy the backend onto the server, keep configuration files in the right place, and make sure the application comes back automatically after a reboot. ...