1. Development vs Production
Wails development mode and the native executable are different
environments.
Development: - Vite development server - Browser-based workflow - Fast
reload
Production: - Native executable - Uses WebView2 directly - Must always
be tested separately
2. Browser Behaviour May Differ
An implementation can work perfectly in browser development mode but
behave differently in the native executable.
Always verify both environments before adopting an architecture.
3. iframe Experiment
Browser Development
- HTTPS works.
- HTTP Basic Authentication works.
- ttyd loads successfully.
Native Executable
- WebView2 environment initializes.
- Process remains alive.
- Native window never becomes visible.
Replacing the iframe with simple HTML restores normal operation.
4. Architectural Direction
Avoid:
Wails
↓
localhost
↓
iframe
↓
labserver
Prefer investigating:
Wails
↓
Native WebView
↓
labserver
Reasons: - Simpler architecture. - Better browser-wrapper design. -
Easier keyboard interception. - Better long-term foundation for
AppName.
Key Lesson
Sprint 0 is about reducing uncertainty.
Discovering architectural limitations early is more valuable than
implementing many features on top of an unsuitable design.