Fair tips, no drama.

My partner works in hospitality. Every time her team split tips, the same debate came back: who worked longer, who is still a trainee, who rounds what. The maths was never the hard part. Agreeing on it was.

That became the brief: a split everyone can see, check and trust.

So Tipza is a calculator and a record. A shift lead adds the total, picks how to split it, and the whole team sees the hours, the rate and their own share. It never touches the money. Payments, payroll and tax stay with the team and the employer.

I reviewed other tip apps and the spreadsheets teams already use, and watched tips being split in real cafés and bars. What I saw was simple: teams needed a clear calculator and a shared record, not another payments tool.

That decided what Tipza would not do.

No payments. It records the splits you enter and doesn’t collect, hold or send funds.

No POS integration and no IT setup. A shift lead can set it up tonight.

Clear for both sides. The person running the split and the people receiving it read the same breakdown.

Before any screen, I defined the visual language as Figma variables: a warm neutral scale instead of grey, a green and a yellow from the brand, Space Grotesk for display and Figtree for reading.

Primitives feed a semantic layer named by role, so a button asks for action primary, never a hex code. Spacing and radius follow the same t-shirt scale, from 2xs to 8xl.

I designed the foundations and every component myself: pill buttons in three colours, three sizes and four states, form fields, calendar ranges, team cards, drawers and a small set of illustrations. Each one reads only from tokens.

Variants carry the sizes and states, and every colour and radius is bound to a variable. Change a token and the library follows.

A playful pizza motif runs through the app: slice icons, a split-pizza illustration and a result screen that says “All slices served!”

Tokens Studio exports the variables to JSON, and that file feeds both the Figma file and the React Native app. Figma MCP gave Codex and Claude the context of each screen, and I built it all in Cursor with Expo.

I coded it alone. Vibe coding is fast, but some nights it’s just you, an AI and a very confident linter.

Add the total, pick the dates, add the team, then review and share. Split equally, by hours, by points or your own way. The team list carries over between splits, and leftover change can roll to the next shift.

1. 01

   Add the total

   Type the tips for the shift. Round up if you like, and the change is saved until next shift.

2. 02

   Pick the dates

   One day or a date range, with an optional tag for morning, evening, weekend or event shifts.

3. 03

   Add the team

   Hours or points per person. The roster carries over, so the next split starts half done.

4. 04

   Review and share

   Everyone sees the hours, the rate and their share. Every split is saved in a calendar history.

I put working builds in front of hospitality staff and changed what didn’t land. Three changes came straight out of it.

Points for trainees. Not everyone on a shift carries the same load, so each team member has points. There is a 5-point option for trainees.

Swipe to confirm. A swipe now confirms each split.

Shift tags. Optional tags tell a busy weekend from a quiet Tuesday.

The app is free to download. Free covers all four split methods, shareable breakdowns, saved history and up to three team members per split.

Pro unlocks the fourth team member onward, plus Pro Insights: tip trends over 30 days, 3 months and 12 months, tips per hour, a comparison across shift types, and priority support. Pro is an in-app purchase.

Tipza is live on the App Store and Google Play in English and German, with its own website and blog, and it was featured on Product Hunt (opens in new tab). Grok Bot helped with the marketing and the deployment.

An AI assistant to log a split in one sentence and turn history into insight.