/capabilities
Build modules_
Three core build disciplines. Select a module to inspect scope, method and outputs. Each tab has a direct link you can share.
Mobile app development
We build apps for iPhone and Android that behave well under real conditions: a train going into a tunnel, an expired login, a user who has turned notifications off, a phone set to large text. Most projects use a cross-platform framework such as React Native or Flutter so that one codebase serves both platforms, with native modules written in Swift or Kotlin where hardware access or platform conventions demand it.
Before building, we define the offline model — what the app can do without a connection and how it reconciles when it comes back. We design the API contract with versioning so older installed builds keep working when the server changes. Crash reporting, if you want it, is configured with privacy settings that match your disclosures.
Every ten-day cycle produces an installable build through TestFlight or Google Play internal testing. You test on your own device, we log what you find, and the next cycle addresses it.
- Platforms
- iOS, iPadOS, Android phones and tablets
- Stack
- React Native or Flutter; Swift/Kotlin modules as needed
- Includes
- Offline model, auth flows, push notifications, analytics only by consent
- Outputs
- Source repository, build pipeline, test plan, release runbook
- Not for
- 3D games, AR-heavy products, embedded firmware
Web development
From compact company sites to logged-in portals with roles and reporting, we build for the web with a bias towards speed, standards and maintainability. Pages should be usable within a couple of seconds on a mid-range phone over a mobile connection, should work with a keyboard and screen reader, and should not need a specialist to change a paragraph.
For content sites we favour static generation or a lightweight CMS. For applications we use typed frameworks, a relational database where data matters, automated tests for the paths that handle money or permissions, and deployment pipelines that can be rolled back in minutes. We set a performance budget early and report against it each cycle.
Accessibility is engineered in: semantic structure, visible focus, labelled controls, sufficient contrast and motion that respects user preferences. We target WCAG 2.2 AA and document which checks were run.
- Builds
- Corporate sites, portals, dashboards, booking and internal tools
- Stack
- Static generation, TypeScript frameworks, PostgreSQL, PHP where hosting requires
- Includes
- Performance budget, accessibility review, security headers, CI pipeline
- Outputs
- Repository, environment docs, editor guide, rollback procedure
- Not for
- Very large product catalogues — a specialist commerce platform fits better
UI / UX design
Interface design at Nexion starts with observation. We speak to the people who will use the product — or the staff who field their questions — and look at whatever evidence exists: support emails, search logs, abandoned forms. From that we map the critical tasks and where they break.
Wireframes come next, intentionally plain so attention stays on structure and wording. We test them with a small group of representative users, fix what fails and test again. Only then do we move to the visual layer: type scale, colour tokens, spacing, components and motion, each with every state defined — default, hover, focus, active, disabled, loading, empty and error.
The output is a design system developers can build from without guessing, plus a prototype stakeholders can click through before a line of production code is written.
- Methods
- Interviews, task analysis, journey maps, usability tests
- Artefacts
- Wireframes, clickable prototype, component library, tokens
- Includes
- Contrast and focus checks at design stage, content guidance
- Outputs
- Design files, findings report, developer handover session
- Not for
- Brand identity and naming — we partner with specialists
Composite builds
Most projects combine modules. A typical new product moves through M3 → M1 or M2 → M4 → M5. You can enter at any point; we will review what exists before recommending the next module. Publishing and support are covered on their own pages: M4 store publishing and M5 operations.