See what business websites and web or mobile apps tailored to specific processes can look like. We first show what is actually included in each demo, then outline potential integrations and a full implementation.
Clear status disclosure: the projects shown here are interactive demos. They present the visual layer and selected user journeys. A backend, real payments, automated messages, administration panels and app publishing would be part of a potential implementation.
PROJECT 1 · WEB
INTERACTIVE DEMO
PD AW — towing and car rental in two separate user journeys
One demo, two very different contexts: an urgent roadside assistance request and a more considered car selection and booking process.
What the demo shows
a dedicated towing request flow with a pickup address or the option to generate a location pin;
a vehicle catalogue, filters, car selection and booking calculation;
a simulated online payment step — without processing a real transaction.
Potential development
connecting a live payment gateway for rentals and towing services;
checking fleet availability, recording bookings and sending customer confirmations;
providing the tow-truck driver with the details required for the job: name, phone number and location;
new-request alerts through an app, dashboard, Telegram, WhatsApp or SMS.
01
Project goal
Combine 24/7 roadside assistance and car rental in one service without blending two completely different user situations. A stranded driver needs to submit a request quickly, while a rental customer needs time to compare vehicles, prices and terms.
02
Challenge
The towing flow must support users who are often under time pressure and may not know their exact address, while a car booking requires filters, calculations and a clear summary. The shared interface could not make either journey feel like an afterthought.
03
Solution and architecture
The demo separates both processes from the outset. The towing form lets users enter an address or state that they do not have one, grant location access and generate a pickup pin. In a full implementation, the user’s name, phone number and location could be sent to the appropriate driver. The rental module could check availability, save the booking and initiate a real payment, while the team receives an automatic notification through the selected channel.
04
UI / UX
Black and gold strengthen brand recognition, but the action hierarchy matters most: requesting assistance, choosing a car, reviewing the summary and paying remain separate, concise steps. Large controls and simple messages also make the service easy to use on a phone.
05
Design outcome
The interactive demo presents the full logic of both journeys without pretending that a live backend is already in place. Once connected to a backend and payment provider, the solution could organise requests, reduce manual data entry and pass job details — including an address or location pin — to the driver more quickly.
towing and rentalonline bookingspaymentslocation and alerts
PROJECT 2 · WEB
INTERACTIVE DEMO
Kraków REX — property presentation and structured lead generation
The website combines the image of a premium local agency with property search and a clear path from interest to enquiry.
What the demo shows
presentation of the brand, listings and selected developments;
filtering, search and a map that helps users understand each location;
contact, meeting and property valuation forms, including a hidden pop-up linked to a specific listing.
Potential development
CRM integration for enquiries, contact history and case statuses;
assigning leads to advisers and sending meeting reminders;
notifications about new enquiries through Telegram, WhatsApp or SMS.
01
Project goal
Create a digital home for a property agency that is more than a list of adverts. The website should build trust in local expertise, help visitors browse listings and also serve owners interested in a valuation or sale.
02
Challenge
A large number of parameters can easily turn a property website into a technical catalogue. Price, floor area, property type and location had to be combined with an emotional story about the city where the agency operates. At the same time, the page could not be cluttered with every form at once or lose track of which listing an enquiry concerned.
03
Solution and architecture
The modular structure brings listing cards, filters and a map together. The meeting form remains hidden in a pop-up until a date is selected, while an identifier passed in the background ensures that every enquiry “knows” which property it concerns. The CRM itself is not part of the demo. In a full implementation, however, the website could send enquiry data to it, assign the case to an adviser, maintain contact history and trigger a new-lead alert or a reminder before a meeting.
04
UI / UX
Editorial typography, light and city photography create a premium brand character. Filters, the map, listings and contact prompts share one hierarchy. The form opens only when needed, keeping the page visually clean without making the user lose the context of the selected property.
05
Design outcome
The demo shows how an agency’s image can work together with the website’s sales function. The pop-up form collects structured information and associates it with a specific listing. A future CRM integration could support enquiry handling and advisers’ work — without suggesting that such infrastructure is already part of the presentation.
premium propertyfilters and maplead formspotential CRM integration
PROJECT 3 · MOBILE
INTERACTIVE DEMO
24/7 Roadside Assistant — a mobile concept for driver and fleet coordination
The user app organises driver identity, vehicle parameters and the availability data needed to assign jobs.
What the demo shows
initial driver and vehicle setup;
availability status and essential operational information;
a mobile interface designed for quick use in the field.
Potential development
a backend and administration panel — not included in the current demo;
job assignment, geolocation and status updates;
push notifications and emergency SMS messages.
01
Project goal
Design a simple mobile layer for tow-truck drivers that lets them specify their availability, vehicle and range of possible jobs. Ultimately, the dispatcher should have one up-to-date view of the fleet instead of gathering information through multiple calls.
02
Challenge
Drivers use the app in a busy environment and cannot work through lengthy forms. At the same time, the system should distinguish vehicles, load capacity, location and availability to reduce incorrect assignments.
03
Solution and architecture
The demo covers the driver-facing layer. A full version would require an API and administration panel, neither of which is currently shown. The server could update the fleet’s position and status, then send new jobs to the appropriate drivers through push notifications, with SMS as a fallback channel.
04
UI / UX
Large controls, clear statuses and a limited number of decisions make the app efficient to use while parked or working in the field. The initial setup collects only the information needed to identify the driver and vehicle.
05
Design outcome
The project presents a clear foundation for a fleet coordination system. Only a backend and dispatcher dashboard would turn it into a complete operational tool, so the description clearly separates the working demo interface from potential infrastructure.
AURELIA — service bookings and a beauty salon loyalty programme
The mobile customer journey combines appointment booking, the next scheduled visit and loyalty programme benefits.
What the demo shows
selection of a treatment, date and appointment type;
a view of the next appointment and visit history;
a loyalty card, points and available rewards.
Potential development
a backend and salon dashboard with staff calendars — outside the current demo;
synchronisation of availability, bookings and points;
push or SMS confirmations and optional deposit payments.
01
Project goal
Bring bookings and the loyalty relationship into one app so customers can schedule appointments outside salon hours, check upcoming visits and see the benefits of their points programme.
02
Challenge
The app could not feel like a technical calendar. It had to preserve the brand’s boutique character while guiding users through the service, day, time and confirmation without mistakes or unnecessary screens.
03
Solution and architecture
The demo shows the customer journey. A full implementation would require a backend and salon dashboard to synchronise staff schedules, bookings and points. The server could send neutral push or SMS confirmations and, where needed, initiate a deposit payment through a payment provider.
04
UI / UX
A soft palette, elegant typography and large tiles preserve the premium character of the service. Each screen answers one question, while the bottom navigation provides quick access to appointments, rewards and the profile.
05
Design outcome
The interactive version shows how self-service booking can work together with loyalty and the brand’s aesthetics. An administration panel and live calendar synchronisation remain part of a full implementation, not a hidden feature of the demo.
mobile bookingsservice calendarloyalty programmenotifications
PROJECT 5 · MOBILE
INTERACTIVE DEMO
Installer dashboard — mobile job and field documentation management
One place for the schedule, customer details, job status, navigation and documentation required by the field team.
What the demo shows
a job list and daily schedule;
customer details, address, navigation and status updates;
the work progress and a place to document completion.
Potential development
a backend and office dashboard — not included in the current demo;
storing photos, statuses and job history in one database;
office notifications and customer SMS messages about arrival or completion.
01
Project goal
Give the installer one tool for the entire working day: from checking the schedule and customer details to navigation, status confirmation and completion documentation. Ultimately, the office should be able to follow progress without repeatedly calling for updates.
02
Challenge
Job information is often scattered across paper notes, messaging apps, maps and photo galleries. In the field, the interface must withstand time pressure, accidental taps and less-than-ideal operating conditions.
03
Solution and architecture
The demo groups essential information around a specific job. In a full version, the backend would store statuses and documentation, while the office dashboard would show current progress. The system could also send the customer an SMS about the planned arrival or completion.
04
UI / UX
High contrast, clear statuses and large buttons suit work in a vehicle and on a construction site. The most common actions are available without digging through menus, while external navigation can open in the team’s preferred app.
05
Design outcome
The concept presents a consistent fieldwork journey and a way to organise data around a single job. Only integration with a backend and office dashboard would create a shared history of work, photos and customer communication.
field jobsjob statusnavigationphoto documentation
PROJECT 6 · MOBILE
INTERACTIVE DEMO
Ostoja — a trusted patient app supporting work between sessions
The private user layer organises appointments, tasks, materials and the patient’s own notes.
What the demo shows
appointment history and booking, tasks and materials;
an emotion journal, therapeutic agreement and calm navigation;
a PIN screen as a demonstration of access protection.
Potential development
a secure backend and therapist dashboard — outside the current demo;
precise permissions, encryption and informed user consent;
neutral push or SMS reminders only, with no sensitive content sent through messaging apps.
01
Project goal
Create a calm space that helps patients organise sessions and independent work, with easy access to appointments, tasks, materials, a journal and the therapeutic agreement. The tool should support contact with a specialist, not replace it.
02
Challenge
Mental health requires discretion, sensitive language and reduced cognitive load. The app must not diagnose, create a false sense of security or send sensitive information through inappropriate channels.
03
Solution and architecture
The demo shows the patient-facing layer and a PIN screen. A full version would require a secure API, appropriate permissions and a therapist dashboard, none of which are part of the presentation. Notifications should remain neutral, and clinical data should never be sent through Telegram or WhatsApp.
04
UI / UX
A gentle colour palette, light and a calm interaction pace reduce pressure. Modules are separated by user intent, while crisis information remains easy to access regardless of the other features.
05
Design outcome
The concept shows how to organise work between sessions without pretending to be a medical tool. Any implementation would require a dedicated approach to security, consent, data retention and specialist access — not merely a few additional screens.
privacy by designpatient appneutral reminderssecure API