Preparing the machine.

A / 06

About

DOSSIER

Developer and designer, from Brazil.

ROLE
DEVELOPER + DESIGNER
BASE
BRAZIL / REMOTE
LANGUAGES
EN / PT-BR
Tulio Cunha / Computer SystemsINDEX 07 / 08
A / 06DOSSIER

One practice. Every layer.

I design and engineer software as one continuous system, from the product decision to the interface, runtime, and infrastructure that make it real.

Tulio Pinheiro Cunha
PRACTICE
TULIO PINHEIRO CUNHA
DETAIL ON FILE
CARDMANIACS / NATIVE READING
EXPOSURE / PRINTA / 06
DOSSIER RECORDSERIES / ARCHIVE
01CAPABILITIES / WHAT I BUILD

Five things I build for clients.

Design and engineering under one roof, for companies abroad and in Brazil.

01

Full-stack web products

PROOF:Nomadz Trips

Web apps, platforms and portals built end to end: interface, API, database and deployment, shipped on fast edge infrastructure.

  • SaaS and internal platforms
  • Client portals and dashboards
  • Headless CMS and publishing
  • APIs, auth and payments
02

Web design and interfaces

PROOF:LDR Advogados

Marketing sites, product interfaces and design systems with a strong typographic point of view, designed and built by the same person.

  • Websites and landing pages
  • Product UI and UX
  • Design systems and components
  • Brand on the web and motion
03

Immersive 3D and 2D experiences

PROOF:This site, on film

Interactive WebGPU and Three.js scenes, scroll-driven stories and motion that stay smooth on real devices, like the machine on this site.

  • Real-time 3D for the web
  • Shaders and post-processing
  • Scroll-driven storytelling
  • Product showcases and configurators
04

Native Apple apps

PROOF:Cardmaniacs

iPhone, iPad and Mac apps in Swift and SwiftUI, with widgets, extensions, offline data and iCloud sync, built to feel at home on the platform.

  • iOS, iPadOS and macOS apps
  • Widgets, App Intents and extensions
  • Local-first data and CloudKit sync
  • App Store release
05

Backends, systems and infrastructure

PROOF:Flying Dutchman

APIs, servers and databases, and the infrastructure under them: distributed services, networking, containers and edge deployments that stay fast and observable.

  • APIs and backend services
  • Databases and data pipelines
  • Cloud, edge and container infrastructure
  • Performance and reliability work
02PRACTICE / PROOF ON FILE

Three decisions on file.

I work one way across native applications, backend systems, and the web. These three are filed where you can inspect them.

01

A reading system, not a pile of tools

NATIVE READING / APPLE

Cardmaniacs holds feeds, saved articles, bookmarks, highlights and documents in one local-first workspace. The architecture is a modular monolith, not a global bag of state.

FILED:CARDMANIACS

02

Boundaries around the store

PERSISTENCE / SWIFT

BoutiqueDB-Swift wraps Turso in a native Swift persistence layer with live observation and CloudKit sync. It is the framework, not the engine.

FILED:BOUTIQUE DB

03

A front page that reads like print

CLIENT RECORD / WEB

The Offside leads with one story and a full-bleed photograph; the desk and the features file beneath it. Capture, not mockup.

FILED:THE OFFSIDE

03METHOD / HOW A PROJECT RUNS

How a problem becomes a system.

My working loop across native applications, backend services, and interactive graphics.

  1. 01

    Read the constraint

    I frame the actual limit before proposing anything.

    Platform ceilings, frame budgets, operational dependencies. A problem becomes a system when its boundaries are written down first.

  2. 02

    Draw it before building it

    Design names the parts; the build corrects the drawing.

    Composition and implementation inform one another in both directions. Neither is decoration for the other.

  3. 03

    Ship the smallest whole

    I implement the vertical slice directly.

    The smallest coherent system that proves the model, verified running rather than documented.

  4. 04

    Measure where it runs

    Quality is assessed on target hardware.

    Profiled on the device, read in the browser, operated under load. What cannot be measured there is not finished.

WORKING COMMITMENTS

01PRODUCTS THAT LAST
I engineer for the maintainer years later, not for the demo.
02SYSTEMS THAT SCALE
Deterministic under load, verifiable under failure, and legible to whoever operates them.
03EXPERIENCES THAT RESPECT THE USER
Fast, quiet interfaces that preserve focus: no artificial delays, no manipulation.
04MEMORANDUM / ABOUT ME

Why I work across the whole system.

Software engineering frequently fractures into artificial silos: native engineers who ignore distributed systems, backend authors who treat interfaces as secondary decoration, and web developers who never inspect the hardware beneath the browser.

I have always found those divisions counterproductive. Understanding memory architecture, operating system scheduling, data pipelines, and GPU shader execution is not a disparate list of interests. It is what makes an application fast, robust, and dependable.

When one person holds the whole system, the interface and the infrastructure stop disagreeing. That continuity, from the operating system to the pixel, is what this site is built to demonstrate.

ARGUED AT LENGTH:CLOUDFLARE WORKERS ISNT SERVERLESS ANYMORE

END OF RECORDPERSON
DOSSIER ENDS / CONTACT OPENS
START A PROJECT

SIDE B

SOURCE

Source.

Open source, libraries, servers and experiments live on GitHub, public as soon as they are ready to be read.

LiqUIdify, BoutiqueDB-Swift and the tools behind this site are filed there.

github.com/tuliopc23