/ Services
Everything a product needs.
One team from the first sketch to the store listing. We do product design, web applications, mobile apps, and the search and performance work that decides whether any of it gets found.
Product design
Interfaces that are obvious the first time and still fast the hundredth.
We start from the job the product has to do, not from a moodboard. Flows, states and edge cases get designed before anything is styled — the empty list, the failed payment, the sold-out item — because those are the screens that decide whether people come back. What ships is a real design system with tokens, components and rules, not a folder of mockups that the build then argues with.
What you get
- User flows and IA
- Design system and tokens
- High-fidelity UI
- Interactive prototypes
Web applications
React front ends and the APIs behind them, built to be maintained.
Typed React on Vite, server rendering where a page needs to be found, a real data layer with cache invalidation that actually invalidates, and a bundle budget the build enforces rather than a lint rule nobody reads. We build the operator side too — the dashboards, the moderation tools, the admin console — because most products are two-thirds internal software wearing a public front end.
What you get
- Marketing sites and web apps
- SSR and static rendering
- Dashboards and admin tools
- REST integration and auth
Mobile apps
One React Native codebase, two stores, native where it counts.
Cross-platform apps that do not feel cross-platform: native navigation and gestures, push notifications that deep-link to the right screen, sensible behaviour on a bad connection, and the store submission handled. We ship the same design system the web app uses, so the two surfaces stay recognisably one product instead of drifting into two.
What you get
- iOS and Android from one codebase
- Push and deep links
- Offline-tolerant data
- Store submission
Shipped in Zthrifts.
SEO, AEO and performance
Getting found by search engines and by the answer engines replacing them.
Structured data that resolves to one entity, real HTML for crawlers that do not run JavaScript, canonical and sitemap discipline, and Core Web Vitals treated as a build failure rather than a report. Increasingly that means writing for two audiences at once: classic search, and the AI answer engines that cite a handful of sources — which is why every site we build ships a machine-readable summary of itself alongside the sitemap.
What you get
- Technical SEO and structured data
- AI answer-engine optimisation
- Core Web Vitals
- Merchant feeds and analytics
How we build.
What technologies does Yahatech build with?
React and TypeScript on Vite for web, with Node for server rendering and APIs; React Native for iOS and Android from a single codebase; React Query for data and cache; and Tailwind or hand-written CSS design systems depending on the product. We choose boring, well-supported tools on purpose — the interesting part of a product should be the product.
Do you build both the customer-facing app and the internal dashboards?
Yes, and we prefer to. Most products are two-thirds internal software wearing a public front end — the seller tools, the moderation queue, the admin console. Building both sides against one design system is what keeps them from drifting into two different products, and it is where a lot of the cost of a rebuild usually hides.
What is answer-engine optimisation, and why does it matter now?
Classic SEO assumes a person reads a list of links. AI answer engines — ChatGPT, Perplexity, Claude, Google AI Overviews — read a few sources and write the answer themselves, and most of their crawlers do not run JavaScript. So a client-rendered site that ranks fine in Google can be invisible to them. We ship real HTML for crawlers, structured data that resolves to a single entity, and a plain-text summary of the site at /llms.txt that an answer engine can read directly.
Know what you need?
Let's scope it.
Send the shape of the problem. We reply within one business day, usually with questions.