Work record

Work: what we have built

Short answer

On this page: 1 delivered work, 3 publications we built and shipped, 2 of our own projects, and 5 demos. Every card states which one it is, because presenting work as something it is not destroys the only thing worth having here. A client's name appears only with permission, or when the client already credits us publicly — so this count is not the total number of projects we have done.

You will not find percentages or growth figures here: we do not print a number we have not measured or are not allowed to share. In this site's code a metric can only be entered with its source and measurement date — a sourceless figure fails the build.

LabyraWork tally

TypeCount

  • Delivered1

    Built for a real business and handed over

  • Live3

    A publication we built and shipped end to end

  • Our own work2

    Labyra's own business, or the family company

  • Demo / concept5

    No real company behind it — a demonstration we built

Total11

labyra.co/en/work

Entries 11

Private tutoring / academy · 2026
Delivered

Farhsan Academy

A website we designed and delivered for a private tutoring academy. Handed over on its own domain, mobile-ready, with technical SEO already in place.

What we did

  • Website design and development
  • Own domain, SSL and go-live
  • Technical SEO and metadata setup
  • Google Ads campaign setup

Full control of the site is being handed to its owner, which is why we do not call them "our client" — it is work we designed and delivered.

Mobile app / business software · 2026
Our own work

CepSalon (iOS + Apple Watch)

The mobile app of our booking system (formerly Labyra Randevu): a native iPhone and Apple Watch app written from scratch. Its first version passed Apple's review and went live on the App Store on 21 August 2026; version 2.0, released on 30 September 2026, carries the CepSalon name.

What we did

  • iPhone app (Swift / SwiftUI)
  • Apple Watch app and watch-face complication
  • Push notification infrastructure (APNs)
  • Store release: icon, screenshots, privacy labels, age rating

Technical note

  • Reads go straight to the database under row-level security: the database, not the client, decides which business sees which record.
  • Conflict checks, email and calendar-file generation stayed in a single web service and were never duplicated in the app.
  • Notifications carry no phone number, email or customer note — only time, service and an abbreviated name.

This is our own product, not client work. It is listed here because it is the one verifiable example of our mobile app development: the store listing is public.

Construction · 2026
Our own work

Ünal İnşaat

A corporate site for our own family business. Not client work — it is listed here because we use it ourselves.

What we did

  • Corporate brochure site
  • Services and reference sections
  • Mobile-ready design

This is not a client reference, it is our own business. We say so plainly.

Publishing / content platform · 2026
Live

KOBİ Dijital

A content platform publishing technology guides for small businesses: e-documents, inventory, automation and digital marketing. Design, infrastructure and publishing pipeline built end to end by us.

What we did

  • Publication design and Next.js infrastructure
  • Category structure, RSS and technical SEO
  • Content structure and publishing-routine setup
Publishing / regional technology · 2026
Live

Egebit

A publication covering technology, manufacturing and software across the Aegean region (İzmir, Manisa, Aydın, Denizli, Muğla). Design and infrastructure built end to end by us.

What we did

  • Publication design and Next.js infrastructure
  • Region-focused editorial structure
  • Content structure and publishing-routine setup
Publishing / software development · 2026
Live

Kod Defteri

A platform publishing Turkish software engineering notes: architecture decisions, tooling choices, lessons from production. Design and infrastructure built end to end by us.

What we did

  • Publication design and Next.js infrastructure
  • Archive and RSS setup
  • Content structure and publishing-routine setup
Industrial manufacturing (gearboxes) · 2026
Demo / concept

HALDENBERG

A four-language demo built to show what a B2B manufacturer's site abroad can be. There is no real company behind it.

What we did

  • Four-language site (German, English, French, Spanish)
  • 170-variant catalogue and a selection tool
  • Technical datasheets generated as PDF
  • Interactive 3D product view

Technical note

  • Translated URLs per language, cross-linked with hreflang
  • The selection tool reads the product catalogue itself — no second list to drift out of sync
Prefabricated timber construction · 2026
Demo / concept

AURENBACH

A five-language demo for a prefabricated timber manufacturer. The insulation calculation on it follows the actual standard.

What we did

  • Five-language site (German default, Turkish included)
  • Exploded wall build-up animation
  • Insulation (U-value) calculator

Technical note

  • U-values follow EN ISO 6946 — timber fraction included, no invented coefficients
Aluminium systems · 2026
Demo / concept

ORBAIZ

A five-language demo for an aluminium systems house, built around the distinction between a systems house and the fabricators who make the windows.

What we did

  • Five-language site (Spanish default, Turkish included)
  • Thermally broken profile section, visualised
  • Window performance (Uw) calculator

Technical note

  • Uw is calculated to EN ISO 10077-1
Café / restaurant · 2026
Demo / concept

KÖZ

A single-page, scroll-driven premium demo for cafés and restaurants. The brand is fictional.

What we did

  • Single-page design
  • Scroll-driven motion and transitions
  • Menu and contact sections
E-commerce / boutique · 2026
Demo / concept

Mylove

An experiment in cinematic scrolling for boutique e-commerce. Product and brand are fictional.

What we did

  • Cinematic product presentation
  • Scroll-driven scene transitions
  • Mobile-ready layout

Questions

Frequently asked questions

Why are there not more client references here?

Because we do not publish a client's name without permission. Not every delivered project is listed here — only the ones where we have written consent, or where the client already credits us publicly on their own site. The permission round is ongoing and the list grows as approvals come in. So the number of entries here is not the number of projects we have done; it is the number we are allowed to publish.

What is the difference between a demo and client work?

A demo is something we built end to end with no real company behind it; the brand name is invented too. Client work is a site built and delivered for a real business. Every card is labelled so the two are never confused. Demos exist to make "we can build this" concrete — handing over an address that actually opens is more honest than a screenshot.

Why are there no percentages or growth figures on this page?

We do not print a number we have not measured, or are not allowed to share. Claims like "300% more sales" mean nothing without a source; in this page's code a figure can only be entered together with its source and measurement date, otherwise the site does not compile. When we have measured, shareable data it will appear here with its source attached.

Last word

Let the next one be yours

Tell us what you need; we will pin down scope and price together.