PostgreSQL – Smartup

Stadion Sports Center

Smartup — Wed, 07 Oct 2026 12:18:42 +0000

A historic sports club, run from one platform.

Stadion is the digital platform of Stadion Sports Center, a historic multi-sport venue with tennis, padel, pickleball, golf simulators, a gym, group classes, a restaurant and a private members’ Clubhouse. It replaces phone calls, spreadsheets and front-desk paperwork with one connected system. Members book a court, invite friends, pay and manage their membership from the web or their phone. Staff run the whole venue from one live back-office: courts, classes, coaches, pricing, memberships, reports and the Clubhouse. We designed and built every part of it: the customer web app, the iOS and Android member app, the staff back-office and the cloud API behind them, connected to Stripe, Salesforce, SoftOne ERP and the venue’s door-access system.

Booking a court meant a phone call or a trip to the front desk. Availability lived in spreadsheets, payments and invoices were handled by hand, and member details had to be kept in step across the venue’s ERP and CRM. Every sport came with its own rules: floodlights after sunset, coaches with their own fees, guests with a yearly visit cap, children booked by their parents, and a cancellation policy that has to be applied fairly every time.

On top of that sits the Clubhouse, a private members’ club where discretion matters: invitation-only access, event requests, referrals and sensitive health information that has to be protected by law. The venue needed one system that members find effortless, and that staff can trust to apply the rules without exceptions.

Four parts share one backend. The customer web app and the iOS and Android member app are where members book, pay and manage their membership. The staff back-office is where the front desk, managers and coaches run the venue day to day. A cloud API connects them all, so whatever staff change shows up for members straight away, and the reverse.

The platform plugs into the systems the venue already runs. Stripe handles card payments, SoftOne ERP keeps customer data and invoicing in step, Salesforce receives Clubhouse accounts, event requests, referrals and approved cases, and Genetec opens the Clubhouse door from a member’s phone.

The home screen opens on a card for each sport, controlled by the venue from the back-office. Members pick a date and a time window and see every free court, grouped by sport and filterable by features such as Central, Covered, Hard or Clay. The time-slot grid prices the booking as they choose and blocks anything that clashes with their other bookings. Evening slots offer floodlights, because the app knows when the sun sets. Members can add a coach (with the lesson fee shown up front), book for a child on their account, or join a waiting list for a full slot and get it automatically if it frees up. Full Members get an all-day gym pass in one tap, and the restaurant uses the same flow with party size, dietary requirements and special requests.

Members can invite other players to share a court, searching members by name or inviting guests by email. The app checks for duplicates and guest-visit limits, and warns when someone is close to their yearly cap. When the players change, a plain message explains what that means for the price: an extra amount, a refund to the wallet, or a lower balance due. Venue rules say a session has a coach or invited players, never both, and the interface makes that clear without losing anything the member already typed. Invitations from other members arrive with Accept and Decline.

Bookings wait in a cart with a live countdown while the slots are held. The cost is broken down line by line: court price, peak-hour charges, lights, guests, coach fee, coupons, wallet use and total. Coupons are matched to each booking automatically. Members with saved business details (VAT number, tax office) can choose a formal invoice instead of a receipt. Payment happens on a secure Stripe page, and bookings fully covered by credits confirm instantly. On the web, a personal QR code then works as the member’s access key to the venue. Before cancelling, members see exactly how much they’ll get back under the venue’s policy.

The Stadion Wallet shows three numbers: the available balance, the total balance, and funds held for upcoming bookings, which are charged only once the service has happened and released straight away on cancellation. Members top up by card, filter every transaction by date and type, and keep an eye on their Stadion Points: a weekly court allowance that comes with subscriptions, with a built-in explanation of how points are earned and spent.

A weekly timetable shows every group class with its coach, studio, price and places left. Members enrol in one tap, join a waitlist when a class is full, and cancel with an automatic refund. The Our Coaches page gives every coach a profile with photo, sports, certifications, years of experience and a bio in Greek and English.

A private area that appears only for members the venue has invited. From the app, members unlock the Clubhouse door with one tap through the venue’s access-control system. A three-step wizard books a venue tour or requests a private or corporate event; each request gets a reference code, goes straight to Salesforce, and can be followed from “under review” to “confirmed”. Members can refer a friend, with an optional supporting document, and follow each referral’s status. A health profile keeps allergies, conditions and emergency instructions so staff can keep members safe. It is stored only with explicit consent, encrypted, and erased the moment consent is withdrawn. Prospects who aren’t members yet can use a public version of the event wizard, which creates leads in Salesforce and is protected against spam.

The back-office is the venue’s operating system. A live booking grid shows every court and every slot, colour-coded by status. The front desk books on a member’s behalf, choosing who pays and who plays, and checks out by wallet, cash or card. Bookings are moved by drag and drop, with every move checked first, and a right-click closes a court for maintenance. A wizard creates recurring series (every Tuesday at 18:00) with coach availability checks. Group programmes have their own calendar, recurrence rules and attendance. Staff set prices per court, guest pricing by plan and sport, booking windows, guest limits and under-18 rules; they configure membership plans and manage subscriptions with proration; they issue campaign coupons and vouchers; and they broadcast messages by push, email and in-app, scheduled in advance. Reports cover court occupancy, revenue, member activity heatmaps and cancellation trends, and every report exports to Excel. Coaches log in to their own portal to see their lessons and classes.

A REST API on Google Cloud Run in the EU, backed by PostgreSQL, is the single source of truth for bookings, wallets and memberships. The web apps are built in Angular 20 and 19, with standalone components, Signals, lazy loading on every page, and server-side rendering for fast first loads. The member app is built in Flutter for iOS and Android, with a layered structure (screens → view models → services) and reactive streams, so a change to a member’s balance or Clubhouse access updates every screen on its own. Firebase handles sign-in, with a token checked on every API call, plus push notifications on web and mobile, hosting and media storage. The reasoning behind the mobile app’s key decisions is written down in fifteen Architecture Decision Records.

The venue’s rules are enforced by the platform, not by goodwill. Each membership plan has its own limit on active bookings, with a counter members can see. Members who cancel too often are suspended automatically for a set period, with the end date shown clearly. Under-18 rules are set per sport, academy accounts follow their own simpler rules, and members whose plan doesn’t include app booking are told to contact the front desk instead of hitting a broken screen. On the staff side, nine roles (Admin, Front Desk, General Manager, Staff, Coach, Academy, Grid Maintainer, Clubhouse Manager and Customer) each get their own permissions and their own start page, enforced in the interface and on the server.

Privacy and security are designed in. Health data is treated as a special category under GDPR Article 9: explicit consent, encryption, one-click erasure, and every staff view of it audit-logged. Error reports, sent to Sentry, carry only what engineers need: never what a member typed, never health data, and email addresses masked. The web apps ship with a strict Content Security Policy, and payment result pages can’t be opened by typing their address. The web apps release through GitHub Actions, with a preview link for every pull request and separate staging and production environments.

Product design, web, mobile, backend and integrations are all ours. A team of 16. That adds up to more than 1,800 commits on the two web apps alone. Along the way:

2023: the staff back-office, starting as a feedback panel and growing into the venue's operating system
2024: wallet and points, coupons, notifications and membership packages
2025: launch of the customer web app, with booking for every sport, Stripe payments, QR access and push notifications; in the back-office, the live booking grid, drag and drop, recurring bookings, group programmes, coaches, and the Salesforce and SoftOne integrations
Late 2025: family accounts, guest invitations, coach booking, golf simulators, under-18 rules, automatic suspensions and a full visual redesign
2026: invoices and detailed cost breakdowns, academy accounts and a new pricing model; then the Clubhouse, with event planning, referrals, GDPR health profiles and its own back-office; and the native member app with door access from the phone

Web: Angular 20 / 19 · TypeScript · Signals · Tailwind CSS · Angular Material
Mobile: Flutter · Dart · Flutter Hooks · RxDart · go_router · built_value
Backend: REST API on Google Cloud Run (EU) · PostgreSQL
Identity & messaging: Firebase Authentication · Firebase Cloud Messaging
Hosting & storage: Firebase Hosting · Firebase Storage
Payments: Stripe
Business systems: Salesforce · SoftOne ERP
Physical access: Genetec
Monitoring & delivery: Sentry · GitHub Actions

The post Stadion Sports Center appeared first on Smartup.

AHEPA Connect

Smartup — Thu, 30 Apr 2026 06:41:32 +0000

One codebase. One branded app per district.

AHEPA CONNECT is a fraternal organisation with districts across Greece and the United States, each running its own chapters, events and members. We built a member app that ships as a separate branded product for every district, from a single Flutter codebase and one API. District 25 went live for its 1,500 members in Greece. District 6, New York, is built and waiting on the store.

Chapter secretaries kept member lists in spreadsheets that were already out of date by the time they were shared. Event announcements went out on Viber and email, and whoever showed up, showed up — attendance was a printed sheet and a pen at the door, if that. Subscriptions were tracked in a notebook per chapter, which meant nobody at district level could answer a simple question like who has paid this year. News was published on the district website and then re-typed, badly, into whatever channel reached members first.

Every district had the same problem and had solved it slightly differently, so there was nothing to standardise on. The obvious answer — build one app for AHEPA — was wrong: a member in Thessaloniki and a member in New York have different chapters, different languages, different governing documents, and no reason to see each other’s content.

Three things ship together: the member app on iOS and Android, a REST API that serves every district from one deployment, and a web dashboard where administrators do the work that used to happen in spreadsheets.

The app is usable before you sign in. A visitor browsing the store gets the district’s news, chapters and upcoming events with no account, hitting the sign-in wall only on the personal parts — their card, their dues, their documents. That one decision removed the biggest source of drop-off for an organisation whose members are not all comfortable creating accounts.

Every member carries a digital card with their name, member number, chapter and role, and a QR code bound to their ID. At an event, the chapter administrator opens the scanner, scans the card, and the scanner immediately re-arms for the next person. Attendance is recorded as people walk in, including anyone who turned up without declaring. The same object solves identity and check-in, so there is nothing extra to hand out and nothing to lose.

Chapter administrators create events; the district administrator approves before anything is published. Members declare attendance or interest and the counter updates live. Afterwards, administrators see who actually came, and members see their own history — which events they made, which they missed.

District 25 runs a WordPress site, District 6 runs Wix. Content approved in the app publishes to the site, and changes made on the site come back into the app. Nobody re-types anything. The server knows, per district, where to publish and how, so connecting a new district’s site is configuration, not a release.

Subscriptions, event charges and other debts are issued per member, with an amount, a period and a status. Members see what they owe and what they have paid, split into two tabs with a running total. Administrators see the same thing across a chapter or the whole district, and mark entries as settled. Payment itself still happens the way it always has, in person or by transfer — the app is the record of who owes what, not a payment processor.

District 25 bundles its Statute and Regulations in the app, so we put a retrieval-backed assistant in front of them. Ask a question about the organisation and the answer expands to show the documents it came from. It accepts voice input in Greek or English. District 6 does not have it, and in that build the screen, the entry point and the route do not exist in the binary at all.

Every fact that differs between districts — brand name, bundle id, default language, which manuals ship, whether the AI assistant exists — lives in a single enum. No screen in the app checks which district it is running in. When we add a district, the compiler lists everything that has to change, and a build with a missing configuration does not compile rather than shipping a wrong default.

The same discipline runs through the API. Every request carries the district it belongs to, and permission is checked three ways before anything executes: who you are, what role you hold, and whether the thing you are touching belongs to your chapter. A member of one district cannot use another district’s app, and the rule lives in one place.

The result is that District 6 — different brand, different language, different governing documents, no AI — took a fraction of the effort of District 25, and none of it was rework.

Product design, mobile, backend and the admin dashboard were all ours. A team of twelve: product design lead, mobile developers, web developers, backend.

Bilingual throughout, 281 translated strings per language, light and dark themes, and a separate accent palette for administrator screens so privileged actions never look like ordinary ones. iOS release is automated end to end — the build asserts its own bundle id, version, signing certificate and push entitlement before it is allowed near TestFlight.

Mobile: Flutter · Dart · go_router · Provider
Backend: NestJS · Google Cloud Run
Identity: Firebase Authentication
Push: Firebase Cloud Messaging
Data: PostgreSQL · SQLite (on-device)
AI: Retrieval-backed assistant on Cloud Run
Admin: Firebase-hosted web dashboard

The post AHEPA Connect appeared first on Smartup.

PostgreSQL – Smartup

Stadion Sports Center

Stadion Sports Center

A historic club, run by phone and paper

One venue, one live system

Book a court in a few taps

Play together

A checkout that explains every euro

A wallet that shows what's really yours

Classes and coaches

The Clubhouse

Running the venue

One source of truth, many doors

Since 2023, from feedback panel to operating system

Stack

SKAI.gr

Tell us what you're building.

AHEPA Connect

AHEPA

Everything lived in three places and none of them talked

A product, not a project

The membership card is also the ticket

Events that go through approval, not through a group chat

Published once, everywhere

Dues, finally in one ledger

An assistant that cites its sources

Adding a district is adding one line

One team, from idea to store

Stack

AHEPA CONNECT

AHEPA CONNECT D25, Greece

AHEPA CONNECT D6, New York

Tell us what you're building.