KANCHO / Dev

Technologies

Tools and standards behind our work

We choose modern, well-supported technologies that fit each project — not hype for its own sake. Our stack spans mobile, web, backend, CMS, and design, with shared practices for TypeScript, accessibility, and maintainable delivery.

Next you will see how universal design and accessibility guide our work, then current trends in development and design, the platforms we use day to day, and our engineering practices.

Inclusive design

Universal design & accessibility

Accessible products are better products — for people with disabilities, for mobile users, and for everyone who benefits from clear language and predictable interfaces. We align with universal design principles and practical WCAG-oriented checks.

Universal design of ICT

We apply principles from universal design of information and communication technology: solutions should be usable by as many people as possible, without unnecessary adaptation or specialised versions.

  • Design for diverse abilities, ages, and contexts of use
  • Prefer flexible interfaces over one-size-fits-all assumptions
  • Involve real users and constraints early in discovery

WCAG & accessible UI

Web and app interfaces are built with semantic structure, sufficient contrast, keyboard access, and meaningful labels — tested with automated and manual checks where it matters.

  • Semantic HTML, roles, and focus order on web
  • Touch targets, labels, and error messages on mobile
  • Colour contrast and text resizing in light and dark themes
  • Lighthouse, axe, and screen-reader spot checks

Inclusive product patterns

Beyond compliance, we design for clarity: readable typography, logical navigation, loading and error states, and content that works in more than one language when you need it.

  • Plain language and clear hierarchy in UI copy
  • Localization-ready structure for Norwegian and English content
  • Motion and animation used sparingly and respectfully

Our stack

Technologies we use in projects

We combine these tools based on your product — a mobile app may lean on React Native and Node.js; a marketing site on WordPress or Next.js; an online store on WooCommerce with tailored themes.

Mobile

React Native
Expo
Expo Router
TypeScript
EAS Build
Redux
React Query
iOS & Android

Web & frontend

Next.js
React
TypeScript
JavaScript
HTML5
CSS / Sass
CSS Modules
Material UI

Backend & data

Node.js
Express
PostgreSQL
MongoDB
Prisma
REST APIs
GraphQL
Firebase
JWT / OAuth

CMS, websites & stores

WordPress
WooCommerce
PHP
Gutenberg
Advanced Custom Fields
Sanity
Strapi
MySQL

Design & UX

Figma
FigJam
Wireframes
Prototypes
Design tokens
WCAG-oriented review
Responsive layouts

DevOps & delivery

Git / GitHub
GitHub Actions
Docker
Vercel
AWS
CI/CD
Staging environments
Lighthouse

How we work

Engineering practices across the stack

Technology choices only pay off with consistent practices — typed code, reviews, environments, and documentation so your product stays understandable after launch.

TypeScript & code quality

We use TypeScript on most React, Next.js, and React Native projects for safer refactors, clearer APIs, and fewer runtime surprises in production.

  • Shared types between client and server where practical
  • Linting and formatting aligned across the team
  • Pull request review before merge to main branches

Testing & environments

Features pass through development and staging before production. We test critical paths on devices and browsers that match your audience.

  • Unit and integration tests on APIs and core logic
  • Device and cross-browser checks before release
  • Separate dev, staging, and production configuration

Security, hosting & maintenance

Deployments use HTTPS, environment secrets, and sensible update policies — especially for WordPress, plugins, and dependencies that need ongoing care.

  • Auth, HTTPS, and role-based access by default
  • Monitoring, backups, and documented handover
  • Dependency and plugin updates as part of maintenance

© 2026 all rights reserved KANCHO / Dev