Panel Discussion: Winning Web and Native Apps
summary
Panel covers concrete NFR tactics: server rendering on Node to avoid low throughput, use of schema.org JSON-LD and semantic HTML for SEO and accessibility, and linting like ESLint JSX plugin to catch accessibility issues early. Real-world failure: a micro‑frontend project loads 39 microapps creating a 300 MB JS bundle and 25s TTI, later reduced to under 5s by changing loading strategy and educating teams. Tips include automation, web workers/WASM, and on-device AI for discoverability.
AI-written summary · about
chapters (11)
- 0:00Introduction and panelist intros
- 2:33Why NFRs matter as much as features
- 5:45Performance bottlenecks in apps
- 8:10Monitoring and preventing performance issues
- 11:43SEO strategies and discoverability
- 15:58App store discoverability and performance
- 18:43Accessibility in early development
- 23:00Balancing multiple NFRs
- 26:52Trade-offs and platform-level solutions
- 28:15Testing and AI for NFR coverage
- 29:58Summary and key takeaways
