SELECTED WORK · RAZGIBAJMO SE

One centre.
A connected digital experience.

An app, member portal and administration for the everyday work of a fitness centre — with booking rules and shared data behind the scenes.

Razgibajmo se: the app Centre with test data
App · shown with test data
Razgibajmo se: recurring class administration
Administration · schedules and capacity
Razgibajmo se: class programmes in the member portal
Portal · programmes and instructors

HOW RAZGIBAJMO SE WORKS

One centre. Everything connected.

From the first visit to a class booking — each view has its own role, and all work as one system.

01 · FIRST CONTACT

Public website

Classes, instructors and the first contact with the centre.

Access to member services

02MEMBER
Razgibajmo se mobile app with test data

Mobile app

Classes, passes, absences and make-up bookings on your phone.

03MEMBER
Razgibajmo se member portal — class overview

Member portal

The same account and member services in your browser.

04CENTRE TEAM
Razgibajmo se administration — recurring classes

Administration

Members, passes, approvals, schedules and attendance.

ONE SHARED FOUNDATION

The shared backend

Sign-in and permissionsMembers and pass validitySchedules and capacityAbsences and bookings

Interface previews with anonymised names. The app uses test data.

Walk through the example

WALK THROUGH A PRACTICAL EXAMPLE

One absence. Connected changes.

Open the steps to see how a member’s action affects an available place, another member and the team’s overview.

An illustration with fictional members A and B. The counter tracks only the extra place in this example; the class’s actual capacity may differ.

01 · A member reports an absenceConfirmed recurring class → absence reported

Member A selects a session of their recurring class in the app or portal and confirms the absence.

Member A

Absence reported

Extra place in this example

1 place available after confirmation

Member B

No booking yet

WHAT HAPPENS BEHIND THE SCENES

The system checks the confirmed recurring place and the allowed absence reporting window.

RESULT

Member A sees the absence in their reported absences.

02 · The system releases an extra placeSelected class session → one extra place available

The number of make-up places increases for that date and class. Member A keeps their recurring place; the absence applies to the selected session.

Member A

Absent for this session

Extra place in this example

1 place available

Member B

Can select the place

WHAT HAPPENS BEHIND THE SCENES

The absence and released place are tied to a specific class, date and member.

RESULT

Other members can find the extra place in the schedule.

03 · Another member books a make-up classValid pass + available place → booking

Member B selects a make-up class in the schedule and confirms the booking for that session.

Member A

Absent for this session

Extra place in this example

0 places available

Member B

Make-up class booked

WHAT HAPPENS BEHIND THE SCENES

The system checks pass validity on the class date, an available place and any existing registration.

RESULT

Member B sees the booking under their make-up classes; the available place count decreases.

04 · The team sees the updated overviewAbsence and make-up booking → the same class overview

Administration links member A’s absence and member B’s booking to the same class session. The team tracks registrations and records attendance.

Member A

Absence in the overview

Extra place in this example

Place is booked

Member B

Booking in the overview

WHAT HAPPENS BEHIND THE SCENES

Member roles and administrative permissions determine who can view and manage each part of the data.

RESULT

Members and the team use data from the same class session.

Explore the actual screens →

REAL INTERFACES

For members and the people running the centre.

The Centre in the Razgibajmo se app with a test account
The actual app interface, captured with a test account and fictional member data.

01 · MOBILE APP

My class. My pass. My next step.

Members find recurring classes, reported absences and make-up bookings in one place. Key actions are tied to their account and membership conditions.

02 · MEMBER PORTAL

Member access in a browser, too.

The portal provides access to programmes and member services using the same account as the app. Members can use a phone or computer to suit their needs.

Classes, instructors and locations in the member portal
A preview of classes in the portal; instructor names are fictional.
Razgibajmo se administration with recurring class overview
An administration preview; instructor names and the account are fictional.

03 · ADMINISTRATION

The overview the team needs.

Schedules, capacity, member requests and attendance are part of the same working environment. The team manages the rules and actions members use in the portal or app.

THE FULL MEMBER JOURNEY

From the first visit to everyday use.

Bookings are part of a wider system. Accounts, passes, recurring places and the team’s work are connected too.

  1. 01 →

    Explores the offer

    Finds a class and the next step on the public website.

  2. 02 →

    Creates an account

    Uses the same account in the app and portal.

  3. 03 →

    Pass linked

    The team links the pass to the account; validity determines booking eligibility.

  4. 04 →

    Submits a request

    Requests a recurring place in the schedule. The request awaits review.

  5. 05 →

    Team approves

    The team reviews the request. The confirmed class appears for the member.

  6. 06 →

    Manages classes

    Checks classes, reports absences and books make-up sessions.

What if the recurring class is full?

The member can join a waiting list for a recurring place. This has its own queue and review process; a make-up booking applies to one class session.

What does the team manage?

Administration brings together members and passes, schedules and capacity, recurring place requests, class overviews and attendance.

WHAT THE BACKEND DOES

A booking is more than a button.

ELIGIBILITY

The right pass and date

The booking process checks pass validity and the selected class session.

CAPACITY

Available places for a specific class

Absences and make-up bookings are handled for a specific date and according to the centre’s rules.

ACCESS

Actions based on roles

Member access and administrative management have different tasks and permissions.

The project’s technical foundation: Flutter for the app and web interfaces, and Firebase for authentication, data and backend logic.

ELNEIA

From a business rule to a user screen.

Our work on Razgibajmo se connects development of the app, portal, administration and backend processes. We design around members’ and the team’s actions: who does what, under which conditions, and what needs to update.

More about how we work →

ABOUT THIS CASE STUDY

A showcase of implemented development.

The previews are based on the project interfaces; personal names and the administration account have been replaced with fictional demonstration data. Process descriptions are based on the project implementation; feature availability depends on the published version and user permissions. The app view uses test data. Additional options for other industries are agreed and developed for each project.

WORKING WITH US

What takes the most coordination today?

Describe how you welcome customers, manage appointments or handle memberships. Together, we will identify a practical first step for your business.

Contact us
Is this your new site? Log in to activate admin features and dismiss this message
Prijava