Development journal
Notes from
inside the build.
Practical thinking about immersive product strategy, architecture, performance and user experience.
01 · AR product planningHow to plan an augmented-reality product that users understand
Start with the user’s physical context, the problem AR solves and the moment digital content becomes more useful than a conventional screen. Define tracking conditions, supported devices, lighting constraints and recovery states before visual polish.
Discuss this topic ↗02 · VR performanceWhy standalone VR performance must shape design decisions
Frame rate is a product requirement, not a final optimization task. Geometry, textures, lighting, interaction frequency and scene transitions should be budgeted from the start for the target headset.
Discuss this topic ↗03 · WebAR conversionWhen WebAR is the right choice for a campaign
WebAR reduces installation friction and works well for short, accessible experiences reached by QR code. The trade-off is a narrower performance and feature envelope than a native application.
Discuss this topic ↗04 · Unity architectureBuilding Unity products that remain maintainable
Clear separation between data, interface, platform integrations and interaction systems makes testing easier and feature changes safer after launch.
Discuss this topic ↗05 · Computer visionDesigning useful camera intelligence
A computer-vision feature should communicate confidence, handle uncertain results and provide an alternative path when real-world conditions reduce detection quality.
Discuss this topic ↗06 · Location experiencesMaking location-based products reliable
GPS uncertainty, connectivity, battery use, permissions and safe user movement need to be designed as first-class product states rather than exceptions.
Discuss this topic ↗