New pages: our front-end, back-end and e-commerce development work

We have published three new pages that describe a large part of our day-to-day engineering: front-end development, back-end development and e-commerce software development. Each one explains what the work covers, which technologies we reach for and when, how a project runs, and the decisions we help clients make along the way.

On all three, the basics are the same as everywhere at Authect. You talk to the founders who build your project, never a salesperson. A senior engineer leads the work. AI speeds up the routine parts, and an engineer reviews every line before it ships. The repositories, cloud accounts and design files are yours from day one.

Front-end development

The front end is the part of a product people actually touch, so the page focuses on interfaces that load quickly, work for everyone and hold up on every screen, from a budget Android phone to a wide desktop monitor. It covers:

• Custom front-end development: web apps, customer portals, dashboards, and booking and checkout flows built from a component library.
• Takeover and rescue of fragile JavaScript codebases: review first, stabilise the riskiest areas and add tests, without a big-bang rewrite.
• Modernisation and micro-frontends, moving ageing front ends to a modern framework step by step and splitting very large apps only where separate teams genuinely need it.
• Design systems and component libraries documented in Storybook and shared by designers and engineers.
• Accessibility and security reviews against WCAG, with keyboard and screen reader testing and checks for browser-side risks.
• Technology selection: a written recommendation on framework, rendering approach and tooling, with the trade-offs.

React and Next.js are our default for most products, with Vue and Nuxt or Angular where they suit the team or the codebase, and TypeScript on every project we start. The page also compares static generation, server rendering and client-side apps on first load, search visibility and hosting cost, and lists the standards every interface we ship meets, including Core Web Vitals budgets checked on every change, WCAG accessibility, right-to-left layouts where needed and analytics that respect consent.

Back-end development

Every tap, payment and search ends up in the back end: it holds the business rules, keeps data consistent across channels and decides how quickly the product responds. The back-end page covers custom back ends for busy platforms, takeover and stabilisation of systems that have become a bottleneck, cloud-native modernisation in planned stages, architecture and roadmap design, REST and GraphQL APIs and integrations with payment providers, CRMs and ERPs, and security reviews that include AI-specific risks such as prompt injection.

We choose from Node.js and NestJS, Python with Django or FastAPI, Go, and .NET or Java, with PostgreSQL as our default database and Redis, Kafka or managed cloud queues where they fit. The page explains patterns that matter in practice, such as idempotent APIs so a retried request never charges a card twice, and offline-friendly sync for mobile apps. It also compares a modular monolith, microservices and serverless functions honestly: many products are best served for a long time by a well-structured monolith, splitting off services only where it pays.

Each stage of a back-end engagement ends with something you can inspect: assess, design, build, harden (load testing, security checks, backup and restore drills) and then run and evolve.

E-commerce software development

The e-commerce page brings the front and back end together for online selling, for D2C brands and B2B sellers. It covers the whole journey, from the storefront to the order, payment and fulfilment systems behind it:

• Headless and composable storefronts on top of commerce APIs, with content, search and payments as services you can swap.
• Checkout and payment flows with wallets, buy now pay later and local payment methods through providers such as Stripe or Adyen, so card data never touches your servers.
• Marketplaces: seller onboarding, listings moderation, split payments, commissions and payouts.
• Subscription commerce with flexible schedules, pause and skip controls, and graceful handling of failed renewals.
• Order management and fulfilment integrations with warehouses, third-party logistics and carriers.
• B2B ordering portals with trade accounts, negotiated price lists, quotes, approvals and payment on account, connected to your ERP.
• Search, product data and AI merchandising that merchandisers can steer with their own rules.

We work with platforms such as Shopify Plus, commercetools, BigCommerce and Adobe Commerce, and build custom where they stop fitting the business. We are independent of all of them. The page is candid that a theme-based store on a platform such as Shopify is often the quickest and most cost-effective option for a growing brand, and that headless pays off only in specific cases, such as a highly custom experience or several storefronts on one back end. For replatforming, it describes how we move products, customers, orders and URLs across in stages to protect search rankings.

Where to read more

If you are deciding how to split work between the two halves of a product, our guide to front-end vs back-end development explains what each side does and how they fit together. For online selling, the e-commerce software development guide goes deeper into platforms, architecture and when custom work is worth it.

If you already have a project in mind, whether a new storefront, an API that has outgrown itself or a front end that needs rescuing, tell us about it. A founder replies within one working day, and the first conversation happens online, by video call or email.