RTS Questionnaire · Question 19 of 52 · file: answers/q19.html
What other Single Page Application (SPA) frameworks or technologies have you worked with?
SPAReactFrontend
✅ Beyond Angular, I have delivered SPAs with React and Next.js, and worked with additional frameworks and micro-frontend techniques.
🧪 Interactive proof: this answer has its own page with a live cross-framework workflow, the React and Vue code behind it and the acceptance criteria — open the Q19 SPA proof →
Technical detail
- ⚛️ React 19 — function components and hooks, context and reducer state, custom hooks, code splitting with
React.lazy/Suspense, React Router, form libraries, and testing with Jest/React Testing Library. Used in senior front-end roles and as a consultant for public-sector platforms. - ▲ Next.js — file-based routing, server-side rendering/static generation, API routes, and image optimisation for SEO-sensitive products.
- 📱 React Native — mobile SPA-style delivery sharing logic with web codebases for billing, inventory and sales-management applications.
- 🅰️ Angular 17/18 (primary) and historical Vue.js/legacy JS stacks — plus jQuery-era and Ext JS/JSF PrimeFaces rich-client applications earlier in my career, which is useful when modernising old front ends.
- 🧩 Architectural techniques — micro-frontends with Module Federation, shared component libraries published as versioned packages, monorepos with Nx/workspaces, design tokens, and typed API clients generated from OpenAPI/GraphQL contracts.
🎯 I choose the framework based on team skills, SEO/rendering needs, ecosystem fit and long-term maintenance cost — and I can migrate incrementally (for example Angular module → standalone, or page-by-page React adoption inside a legacy app).
🧾 CV evidence: 2025 CV: 'React 19 and React Native', Next.js in core skills, Angular 17/18 as primary; 2023 CV lists FrontEnd Technologies Angular and React; React senior front-end role at Informatica y Buen Gobierno (2023-2024).