The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Simba Voyages - A Production Full-Stack Travel Platform
Simba Voyages is a live travel platform I designed and built for a real client using Lovable.
This wasn't built as a concept or demo project. It is currently live and being used as a client product.
Live Product
https://www.simbavoyages.com/
Admin Portal
https://admin.simbavoyages.com/
What I Built
I built the project as a complete full-stack travel platform with two main applications:
1. Customer-facing travel platform
This is where customers can explore travel services, destinations, hotels, packages and booking options.
2. Admin portal
I also built a dedicated administration platform where the business can manage the operational side of the product, including users, bookings and booking-related activity.
The two sides work together as one product ecosystem.
Customer Booking Flow
A major part of the project was creating a booking workflow that connects the customer experience directly with the business operations.
When a customer submits a booking or expresses interest in a service, the information is passed into the administrative side of the platform.
The business can then see the booking/activity and follow up with the customer using the available communication workflow, including WhatsApp where appropriate.
This means the platform isn't simply displaying travel information — it is connecting the customer journey to an actual business workflow.
Admin Portal
I built a separate admin portal specifically for the client.
The administration side allows the business to manage and monitor the platform rather than relying on the customer-facing website alone.
The admin environment is designed around the operational needs of the business, including:
User management
Customer activity
Booking management
Booking requests
Travel-related data
Managing information used by the customer-facing platform
Monitoring incoming customer activity
Communication/follow-up workflows
This gave the client a dedicated place to manage the platform after deployment.
External Backend Architecture
One of the technical decisions I made was deliberately avoiding Lovable Cloud for the backend.
Instead, I connected the application to an independently managed Supabase project.
The architecture is essentially:
Customer Platform
↓
Application logic
↓
External Supabase backend
↓
Database / application data
↓
Admin Portal
This allowed me to keep the frontend development workflow inside Lovable while maintaining control over the backend infrastructure independently.
It also allowed the customer-facing application and admin portal to work with the same underlying application data.
Flight Search & Booking Integration
Another part of the project I am currently developing is the flight-search experience.
The goal is to allow customers to search for available flights directly through the Simba Voyages funnel instead of leaving the platform.
I have been working on extracting and integrating flight availability information so that users can eventually search for available flights and continue through the booking funnel.
This part of the product is still being developed and refined, so I am intentionally not presenting it as a completed flight-booking API integration yet.
The existing travel platform itself is live and operational.
Product Architecture
The project consists of multiple connected pieces:
Customer Application
The public Simba Voyages platform provides the customer-facing travel experience.
Backend
An external Supabase project handles the backend/data layer instead of Lovable Cloud.
Admin Application
A separate admin portal gives the client control over users, bookings and operational activity.
Communication Workflow
Booking activity can be passed into the client's operational workflow, including WhatsApp-based customer follow-up where appropriate.
Production Deployment
The customer platform and administration platform are deployed separately and connected as one product ecosystem.
Why I Built It This Way
My goal was to build something that could actually be used by a business, rather than creating a simple prototype for demonstration purposes.
The project required me to think about:
Customer experience
Booking workflows
Backend architecture
Data management
Administration
Communication
Production deployment
External service integration
Future scalability
Using Lovable allowed me to move quickly on the product development side while still connecting the application to an external backend infrastructure.
What I Learned
The biggest lesson from this project was that building a real product is much more than creating the frontend.
I had to connect the customer experience to the business's actual operational workflow.
That meant thinking about what happens after a customer clicks "Book", how that information reaches the business, how administrators manage it, and how the platform can eventually automate more of the travel-booking process.
What This Project Demonstrates
Simba Voyages demonstrates my ability to use Lovable as part of a real full-stack product development workflow.
It combines:
Product Design
Frontend Development
Backend Integration
External Supabase Infrastructure
Admin Portal
Booking Workflows
Customer Management
Communication Workflows
Production Deployment
Ongoing API/Flight Integration
Most importantly, this is a live client product, not just a prototype.
I am continuing to develop the platform, particularly around the flight-search and availability experience, while the core travel platform and administrative ecosystem are already live.
Project Links
Customer platform:
https://www.simbavoyages.com/
Admin portal:
https://admin.simbavoyages.com/
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
I think we’re getting dangerously close to the point where “I need a website” no longer means “I need a developer”
I tested @Lovable with one prompt
The result genuinely surprised me.
Built the entire site in a single prompt 👇
Link 🔗 in the comments
Weldone, Ali!
Qloxia - Project Management SaaS Web UI UX Design
Complex workflows deserve clearer interfaces.
Qloxia is a project management and team collaboration SaaS concept designed around a simple product promise:
Bring projects, people, and progress into one place.
The experience combines:
• Project management
• Task management
• Team collaboration
• Planning and analytics
• Progress visualization
• Social proof
• SaaS pricing
• Conversion-focused UX
The design direction uses soft visual environments, editorial typography, rounded components, product-led storytelling, and structured content hierarchy to make the platform feel both professional and approachable.
The goal wasn't to make another dashboard-heavy SaaS website.
It was to create an experience where users can quickly understand the product, explore its capabilities, build confidence, and take action.
Building a SaaS product, dashboard, or web application?
Taqwah can help you transform your product idea into a clear, scalable, conversion-focused UI/UX experience - from strategy and UX to polished interface design.
👉 Send us your product idea and let's discuss how we can design the experience around your business goals.
Project ManagementtaskmanagementsaaswebsiteProduct DesignUX DesignAdobe IllustratorAdobe PhotoshopFigma
Most people set a budget once and forget it exists until it's too late.
This dashboard was designed to fix that. Weekly spending at $24,200, up 12.5% from last month. Monthly budget at $38,543 with 75% already allocated. Budget goals tracked by category salary, investments, freelance, and others each with a completion percentage and a dollar target that makes progress visible before the month ends.
The group contribution panel takes it further. Four members. One shared budget of $5,000. Taylor completed. Morgan at 70%. Quinn at 45%. Jamie cancelled. A collaborative finance tool that makes shared budgeting feel as clean as personal budgeting should.
Upcoming bills electricity, internet, grocery listed before they hit. A spending breakdown table that shows exactly what was budgeted, what was spent, and how much is left in every category.
This is what budget management looks like when the design treats users like they actually want to be in control of their money.
Does this feel like a dashboard that would change how a team manages their finances together? 👇
Designed by Orbix Studio
Tools: Figma
#DashboardDesign #FintechUI #BudgetApp #UIDesign #WebDesign #ContraFreelance #ProductDesign #SaaSUI
This caught my attention immediately. Great use of contrast and visual hierarchy.