Own product · In production

Pagueo: shared expenses with offline work

A PWA for recording, splitting and settling shared expenses without relying on a stable connection.

Open Pagueo
Pagueo: A PWA for recording, splitting and settling shared expenses without relying on a stable connection.

01

Problem

Trips, shared homes and joint purchases create accounts that are hard to maintain. Pagueo removes manual calculations and makes it clear who paid, who owes and which settlements simplify the group.

02

Solution

The application creates events, defines participants, records expenses in different currencies and calculates splits. It organizes and proposes payments between users; it does not move money, process bank payments or connect to banks.

How it works

  • Expenses and participants
  • Automatic splitting
  • Partial payments
  • Suggested settlements
  • Recurring users and invitations
  • Reminders and internal notifications
  • Conversion with real exchange rates

03

Offline-first as a product decision

The interface stores data in IndexedDB and remains usable without a network. When connectivity returns, it synchronizes changes with the API. Offline behavior is part of the main journey, not a secondary screen.

The PWA preserves local changes and synchronizes them with the backend when connectivity returns.
  1. 01PWA
  2. 02IndexedDB
  3. 03API and SQL Server
The PWA preserves local changes and synchronizes them with the backend when connectivity returns.

04

Security and privacy

Identity and JWT protect access to private events. The architecture separates local changes pending synchronization from server-confirmed state.

05

Confirmed stack

  • Blazor WebAssembly
  • PWA
  • ASP.NET Core API
  • Entity Framework Core
  • ASP.NET Core Identity
  • JWT
  • IndexedDB

Interface

The real application on desktop and mobile

Do you need to solve a similar problem?

Let's discuss the real context, data and constraints.

Get in touch