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
Led the Rider Dashboard feature for : e-bicycle platform. Key functionality includes live ride tracking, quick-access emergency SOS, and adaptable ride-mode switching to enhance user safety and control.
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
Trending
retrofuturism
Share your favorite designs from the past exploring the distant future. Or your own take on the aesthetic 🚀
halftone
Dots. Texture. Grain. Let's see your designs using the halftone technique.
Midjourney
Creatives are showing off what they're making with Midjourney.
colorgrade
Video editors sound off: How do you enhance the mood of your video in color grading?
Related posts
One rider. One bike. One forest. One uninterrupted 30-second take.
I wanted to push Seedance 2.5 beyond a beautiful AI shot and test whether it could maintain character identity, bicycle geometry, environment, physics, and complex camera movement throughout one continuous sequence.
From macro drivetrain tracking and high-speed trail movement to a 360° bullet-time orbit and landing — the goal was simple:
Make the impossible camera feel completely real.
Created with Seedance 2.5 for the #ContraSeedanceChallenge.
Pocketride is a ride-hailing app for riders and drivers - book a ride, get matched with a driver, get where you're going. We built it for mid-size Canadian cities like Sarnia, which are too small for the big platforms (Uber etc.) to prioritize but have plenty of real demand. It's currently live with real drivers and riders.
How we built it on Bubble: Server-side recursive dispatch workflows -moved all ride-matching logic off the client so it keeps running even when a driver's phone is minimized or backgrounded, fixing a major reliability gap from client-side timers.
Push notifications via the Devices field - needed for push to reliably reach drivers across app states.
Deep-linked navigation to Google Maps - native mobile doesn't support HTML elements, so we route drivers out to Maps for turn-by-turn instead of building nav in-app.
Twilio SMS as a redundant channel alongside push, so notifications land even when FCM delivery is inconsistent. And, also for phone OTPs while signing up.
Stripe for payments, with QuickBooks Contractor Payments integration in progress for direct driver payouts.
A single shared ride-claim action to prevent race conditions when multiple drivers get notified about the same ride at once.
The fun part of building this on Bubble was proving out a real-time, race-condition-sensitive, notification-heavy system, the kind you'd normally assume needs a custom backend, entirely on the platform.
Amazing work wish you the best!
I've been exploring two hero directions for Yow Island, an island operations management platform.
- Version A uses multiple floating product previews to highlight the platform’s range of features and create a more dynamic first impression.
- Version B focuses on one large dashboard preview for a cleaner, more product-focused experience.
Same message, different visual approach - testing which direction communicates the product more clearly.
Which one would you choose: A or B?
4 voted
80%
1 voted
20%
5 votes
Closed
Cool work !