National research information portal
One codebase, three platforms, a recurring budget line removed.
Client name withheld — covered by a confidentiality agreement.
- 1 → 3
- codebase to platforms
- XX,000 PLN/yr
- recurring saving
- WCAG
- accessibility target
Figure pending confirmation.
Context
Frontend implementation of a public-sector research portal, plus a cross-platform mobile strategy that reused the same repository instead of funding two native applications.
The problem
The institution needed a highly responsive, accessible public portal built from detailed graphic prototypes — and, separately, a mobile presence. The default answer was commissioning native iOS and Android applications, which meant three codebases and three maintenance contracts for one product.
Architecture
One repository, three delivery targets. Every fix and every feature lands once and reaches web, iOS and Android — which is where the recurring saving actually comes from, not from the initial build.
How I built it
Led the frontend implementation, translating complex Adobe XD prototypes into an Angular interface that stayed faithful to the design while remaining genuinely responsive.
Treated accessibility as a requirement rather than an audit item — public-sector reach means keyboard navigation, semantics and contrast are part of the definition of done.
Proposed and built a cross-platform mobile strategy using CapacitorJS, wrapping the same web repository into native shells.
Kept platform-specific code isolated behind a thin layer, so the shared codebase never became a set of branching special cases.
Outcome
- A single codebase serving web, iOS and Android instead of three parallel builds.
- Saved the institution a five-figure PLN sum per year in development and maintenance costs.
- An accessible, responsive public portal delivered faithfully from the original design system.