Aweiro StudioWeb Design & Development

Independent designer & developer · Yerevan

Currently taking on work for 2026

Design and engineering from one pair of hands.

I take a business from a blank page to a live site: the positioning, the palette, the interface, the code, the admin panel the owner actually uses, and the deploy. Six production builds this year — an e-commerce storefront with real card payments, a booking funnel, and four marketing sites. Six design systems, no template between them.

View selected workLet's work together
  1. 01IdeaWhat is this business actually selling, and to whom?
  2. 02DesignA palette, a type pairing and a grid — specific to one client.
  3. 03CodeTyped components, server-rendered, no UI library.
  4. 04ProductDeployed, indexed, and editable by the person who owns it.
Sites built in 2026
6
Design systems written from scratch
6
Off-the-shelf UI kits used
None
01Six projects · 2026

Selected work

Six businesses built in 2026, each with a design system written for it alone. Every screenshot below is the real site, captured from a production build.

Florvale Home landing page: a cream layout with the serif headline “Light that sets the mood” beside a product card.
012026

Florvale Home

A handcrafted-candle storefront with real card payments and an owner-run catalogue.

  • Product design
  • UI design
  • Full-stack development
Preview
Read the case study
Jason Von Flue coaching site: a near-black page with a condensed ember-orange headline and a booking call to action.
032026

Jason Von Flue

A one-page site for a veteran MMA coach, editable by the coach, with git as the CMS.

  • Web design
  • Frontend development
  • Content architecture
Live
Read the case study
Forza Auto Body home page: a near-black layout with the italic condensed headline “Where precision meets perfection” in white and red.
042026

Forza Auto Body

A WordPress replacement for a collision shop — with the brand colour recovered from the logo itself.

  • Brand analysis
  • Web design
  • Frontend development
Built · cutover pending
Read the case study
AlsoAdditional work
05Web Design2026

VERVAR

A gallery-first site for a staircase maker: horizontal work rail, filterable portfolio, one lead form.

Awaiting contentCase study
06Web Design2026

РемСервис

A Russian-language repair service site where the type choice is a layout decision, not a style one.

Placeholder contactsCase study
02Design · Development · Product

What I do

Three practices that only pay off together. A design decision that cannot be built is a mood board; an architecture nobody can operate is a bill.

01

Design

A visual system built for one business, from its own material — its logo, its words, the length of its product names.

  • Web and interface design
  • UX and information architecture
  • Design systems and tokens
  • Colour systems and contrast work
  • Typography and type pairing
  • Art direction, including what not to show
02

Development

Modern React that stays small. Server components by default, client JavaScript only where an interaction earns it.

  • Next.js 15 App Router · React 19
  • TypeScript, strict
  • Tailwind CSS v4 token systems
  • Server components and server actions
  • Hand-written accessible components
  • Performance, SEO and structured data
03

Product

The part that decides whether a site is used a year later: what the owner can change, and what happens when something is missing.

  • Scoping an MVP that can actually ship
  • Content models the owner can edit
  • Admin panels and git-backed CMS
  • Payments, quotes and lead routing
  • Graceful degradation and fallbacks
  • Launch, DNS, handover and documentation
03Five phases, every time

How a project runs

The same five phases every time, whether it is a one-page site or a storefront that takes card payments. The order matters more than the length of any one step.

  1. 01

    Discover

    Understand the business before the brief.

    Who buys, what they are deciding, and what the business has already got — a logo, a phone number, twelve service names, a Facebook page. Most of the design direction is already in that material.

  2. 02

    Define

    Decide the one thing the site is for.

    A quote builder, a catalogue, a booking. Everything designed afterwards either serves that path or gets cut. This is also where I decide what will not be claimed, which is usually the more useful list.

  3. 03

    Design

    Build a system, not a page.

    Colour tokens with measured contrast, a type scale that holds the client's longest words, spacing and motion rules. By the end there is a vocabulary the whole site is written in.

  4. 04

    Build

    Typed, server-rendered, no shortcuts.

    Every component hand-written against the token set. Content lives in a typed model from the first commit, so the admin panel later manages something that has already proven itself.

  5. 05

    Ship & hand over

    Live, indexed, and someone else's to run.

    Deploy, DNS without breaking the client's email, structured data, a documented environment, and a written list of everything still missing. The site should outlive my involvement.

04Background

Coming at design from the other end

I came to design from the other end.

For years my work was back-end and desktop software: Java and Spring Boot services over PostgreSQL, schema migrations, roles and permissions, reporting and exports — later carried onto the web with a Vue front end over the same domain. That work teaches you what a data model costs when you get it wrong, and it teaches you almost nothing about what a good page looks like.

Then I spent a year building an entire product end to end — native client, API, database, deployment — and design stopped being a layer somebody else adds at the end. It is the part that decides whether any of the rest gets used.

Now I do both, deliberately, for businesses small enough that one person doing both is the advantage rather than a compromise. There is no handoff to lose things in. A colour decision and a database decision are made by the same person on the same afternoon, and each one knows what the other costs.

  1. 2023 — 2025

    Engineering

    Enterprise back ends and desktop tooling. Java, Spring Boot, PostgreSQL, Flyway migrations, security, reporting, Excel and CSV pipelines. Then the same domain rebuilt as a web front end.

  2. 2026

    Product

    A full product end to end — native client, API, Postgres, Redis, background workers, CI and deployment. The year that made design non-optional.

  3. 2026

    Design & practice

    Six client sites, six palettes, six type pairings, every component hand-written. Contrast measured rather than assumed; placeholders labelled rather than hidden.

  4. Now

    Aweiro Studio

    Design and build for small businesses and founders — from the idea to the interface to the thing running in production.

On method

On AI-assisted work

AI is part of how I build, and I would rather say so plainly than have it be a discovery. It is very good at the wide, shallow passes: scaffolding a component set, reading a codebase I have not seen, drafting documentation, catching the accessibility issue I stopped noticing three hours ago.

It is not the thing that decides. Every judgement on these six sites was made and defended by a person: that the brand red had to be read out of the logo file rather than copied from the stylesheet, that red text at 3.4:1 fails and has to be lifted, that a condensed Cyrillic face is a layout requirement and not a mood, that gas work stays off a service list without a licence, that an unverified claim is left out even when the page looks emptier for it.

The useful skill is not prompting. It is knowing which of the answers is wrong, and being able to say why.

Toolkit

Listed second is not listed lesser — it is where the work is older or where the tool serves one job. Either way the tools are the least interesting thing on this page.

  • Java
  • Spring Boot
  • Vue 3
  • Docker
  • Redis
  • Prisma
  • Resend
  • Telegram Bot API
  • Vercel Blob
  • JSON-LD
  • Claude Code
  • AI APIs
05On the desk right now

Currently

What is actually on the desk right now — launches waiting on a key, a domain waiting on a cutover, and one component being generalised across every site above.

  • Shipping

    Creator Signature

    A portable “who built this” block for client sites. One folder, no dependencies, eight presentation variants, colours derived from currentColor so it cannot silently lose its palette when copied into a project with different tokens. Rolling out across the sites in this portfolio.

    • React
    • CSS
    • Accessibility
  • Building

    Florvale Home — opening ordering

    Moving the storefront out of preview: live Stripe keys, the webhook verified against real events, shipping rates and delivery times replaced with confirmed ones.

    • Stripe
    • Supabase
    • Launch
  • Queued

    Forza Auto Body — WordPress cutover

    Repointing a live domain from WordPress to the new build without disturbing the nameservers, so the shop's published email keeps working through the switch.

    • DNS
    • Migration
  • On hold

    VERVAR — waiting on the workshop

    Finished and deployable, held back until real photography and confirmed numbers arrive. Every placeholder in it is labelled as one, which is the only reason it is safe to leave sitting there.

    • Content
    • Photography

Currently taking on work for 2026

Have something worth building?

I take on a small number of projects at a time — websites, storefronts, product MVPs, and rebuilds of sites that have stopped earning their keep. If you have an idea and no idea what it costs yet, that is a fine place to start from.

Start a projectvahagn458@gmail.com
  • A first reply within a day, in English or Russian.
  • A fixed scope and a written estimate before anything is built.
  • You own the repository, the domain and the accounts. Always.