Ortica
Let’s talk ↗
Ortica
Let’s talk
ciao@ortica.io

React and Next.js development

Interfaces that respond.
Even with lots of data.

We build web apps and interfaces in React and Next.js, in TypeScript: dashboards, internal tools, portals and headless frontends for ecommerce and CMSs. Whoever designs the screens in Figma also writes the components.

Let’s talk about it ↗What we do ↓
  • React
  • Next.js
  • TypeScript
  • Figma
What we do with React

From components
to the app in production.

  1. 01

    Web apps and dashboards.

    Interfaces people work in all day: filterable tables, long forms, charts, different permissions for each role. They stay fast even with a lot of rows on screen.

    • React
    • TypeScript
    • Dashboards
  2. 02

    Sites and platforms in Next.js.

    Server-side rendering, static pages where they make sense, optimised images. With Payload CMS when you need an admin panel.

    • Next.js
    • App Router
    • Payload CMS
  3. 03

    Headless frontends.

    A React interface in front of Shopify, WooCommerce or a backend you already have, when the standard theme isn’t enough any more.

    • Headless
    • API
    • Ecommerce
  4. 04

    Design systems in code.

    Components designed in Figma become a React library with the same names, variants and states. Whoever adds a screen tomorrow starts from there.

    • Figma
    • Components
    • Accessibility
  5. 05

    Projects to take over.

    React apps stuck on old versions or written by others: we read the code, upgrade step by step and get checks and deploys working again.

    • Upgrades
    • Refactoring

What we work with

Web apps and dashboardsSites and platforms in Next.jsHeadless frontendsDesign systems in codeProjects to take over
ReactNext.jsTypeScriptFigma
React, Next.js or something else?

The right tool.
Not the trendy one.

React is the most widely used library for web interfaces, and that matters: documentation, libraries and developers who can read the code long after us.

We pick React when

  • The interface has lots of states and interactions
  • The same parts come back across screens
  • The project will grow and change hands
  • There’s already a backend or APIs to use

We add Next.js when

  • Pages need to be found on Google
  • First-load speed matters
  • Frontend and API sit better in one project
  • You need an admin panel with Payload CMS
What we look after

Things you don’t see.
Until they’re missing.

  1. 01

    Accessibility.

    Keyboard, focus, labels and contrast planned from the start, not bolted on at the end.

  2. 02

    Speed.

    Less JavaScript shipped to the browser, components loaded when needed, data fetched on the server where it pays off.

  3. 03

    Checks and releases.

    Automated checks on types and key features, and automated deploys to a test environment before production.

FAQ

What we often get asked
about React and Next.js.

How much does a React web app cost?

It depends on the project’s specs: screens, roles, integrations and amount of data. Work on an existing React project is often done with an hours bundle. After a first analysis we send you a written quote.

React or Next.js?

Next.js is built on React: they’re not alternatives. React on its own is fine for apps behind a login; Next.js adds server-side rendering, routing and APIs, which help when pages need to be fast and found on Google.

Can you work on our React project?

Yes. We first read the code, dependencies and deploy setup, then tell you what’s worth keeping, upgrading or rewriting. We can work alongside your team or take the project over.

Do you do frontend only?

Yes. We can build the React frontend on APIs that already exist, yours or third-party, or take care of the Node.js backend too.

What if we also need a phone app?

If the project calls for it, the iOS and Android app uses the same backend as the web app, and we handle publishing to the stores. More on the web and mobile apps page.

Do you work for agencies?

Yes, we build React and Next.js frontends in white label from agencies’ designs. More on the agencies page.

Next serviceNode.js Backends, APIs and integrations in Node.js and TypeScript: the unseen part of web apps, SaaS and ecommerce, tidy and documented.
The next project

A React project?
Tell us about it.

New or to take over: we start from what it has to do and who will use it.

Let’s talk about it ↗I’m an agency ↗

Let’s talk