W

Webink

App

The social and booking network built for tattooing.

Role
Full-stack development
Category
App
Core stack
React Native · Next.js · Supabase
01The context

Tattooing lives on Instagram, a network never designed for it. Artists lose booking requests in overflowing DMs, clients can't filter by style, city or availability, and the algorithm buries the work after forty-eight hours.

02Problem, solution, outcome
The problem

No single platform to discover tattoo artists and studios, follow their work, and book an appointment.

The solution

An app combining a social network, studio and artist profiles, and direct booking with artists and shops.

What it changes

A client finds the artist, follows their work and books without leaving the app. The tattooist stops running their diary out of direct messages.

03The product, screen by screen
Playable mockup

Discover

Brussels · 12 km

AllFine lineBlackworkOld schoolRealism
Mara · fine lineKobe · blackworkLys · floralsNoor · geometry
ExploreFollowingBookingsProfile
01 / 04 · Discover

The filter tattooing never had: by style, city, availability. The image owns the screen, because the image is the pitch.

Interactive mockup rebuilt for this portfolio. The values shown illustrate the interface — they are not production figures.

04The calls I made
01

The portfolio is the product

In this trade, the image is the sales pitch. The whole interface is built around showing the work, not around a feed.

02

Separate artist from studio

An artist may be independent, guesting, or attached to a studio. The data model reflects that reality instead of forcing it into one box.

03

Booking in the same gesture

Discover then book without switching apps or opening a private conversation. That's where the difference with Instagram is won.

05The design board
// palette
#D946EF
#9333EA
#0A0A0C
#F5F5F7
// type scale
AaDisplay · 600
AaHeading · 550
AaBody · 400
// visual calls
  • 01The interface deliberately steps back: magenta and violet frame the page, the tattoo stays the only real colour on screen.
  • 02An irregular mosaic grid rather than identical squares. A portfolio has no standard format.
  • 03Artist and studio pages share a structure but not a density: you don't read a shop the way you read a profile.
  • 04The booking request looks like a short form, not a conversation. That's what makes it processable.
06Why this stack
React Native
The audience is entirely mobile. The web is only a secondary shop window.
PostgreSQL
The relations between artists, studios, styles and slots are genuinely complex. A relational database is the right tool.
Supabase
Image storage and auth shipped with the database, without standing up separate infrastructure.
Next.js
Public profiles need to be indexable. That's a free acquisition channel for the artists.
React NativeNext.jsSupabasePostgreSQLTypeScript

Something similar in mind?

Describe your situation. I'll tell you what's realistic,
in what order, and what I'd do differently.

contact@amauryandrade.com