Building NomadRex has demonstrated that creating software involves much more than producing features. A dependable product also requires clear requirements, disciplined release management, accessibility testing, security controls, documentation, and a realistic understanding of what users need.
Separate products by purpose
One early lesson was the value of separating products by purpose. The Rexdale App, the NomadRex company website, and the Recovery Rx utilities serve different audiences and should not be forced into one oversized application. Each product therefore receives its own identity and user experience while remaining connected to the broader NomadRex portfolio.
Stability before polish
Another lesson was that visual refinement should follow functional stability. For The Rexdale App, core Windows behaviour — including installation, launching, authentication, persistence, routing, restarting, and logout — had to be tested before concentrating on visual alignment. Establishing that baseline reduced the likelihood of design work hiding unresolved technical problems.
Accessibility as a core consideration
Accessibility has also become a core product consideration. Clear navigation, keyboard support, readable contrast, predictable interfaces, and reduced visual clutter benefit far more users than those who formally identify as disabled. Personal experience with concentration, working memory, organization, and task switching has reinforced the importance of interfaces that do not impose unnecessary cognitive effort. See Accessibility considerations for software founders for more on this approach.
Security and configuration as architecture, not afterthoughts
The project also showed why configuration and security should be treated as architectural concerns. Authentication, runtime configuration, protected credentials, server-enforced release controls, security headers, and deployment settings cannot safely be added as afterthoughts. They need to be considered throughout development and tested in the deployed environment. See Security headers and CSP on Cloudflare Pages for a concrete example of this from nomadrex.dev.
AI as an implementation partner, not a source of truth
AI-assisted development has increased the amount of work one founder can complete, but it has not removed the need for human judgment. Generated code and content still require inspection, testing, correction, and alignment with the product's real requirements. AI works best as an implementation partner operating under clear documentation and acceptance criteria — not as an unquestioned source of truth.
Documentation as the connective tissue
Finally, managing several connected products made formal project documentation increasingly valuable. Charters, business cases, requirements, risk registers, decision records, roadmaps, and release criteria help preserve context and prevent projects from drifting as they grow.
NomadRex continues to evolve through this process: define a real problem, establish a stable foundation, test carefully, document decisions, gather evidence, and improve the product without promising more than it can currently deliver.
Related reading: How we build and Product roadmaps and responsible release management.