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
My broader freelance record includes 100% Job Success, but DragSet provides the more useful proof: behavior a client can inspect. Its SwiftUI vehicle deck accepts like and pass actions, advances between profiles, reaches a completed match, and presents a race-challenge action. Firebase, MapKit, messaging, and events define the wider delivery surface without distracting from that central journey. The portfolio lesson is simple: pair a reputation signal with a specific implementation someone else can evaluate.
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
In DragSet, I treated the Send Race Challenge action as more than a button on a successful match screen. It is the handoff that proves vehicle discovery produced something the user can act on. I kept the like/pass deck, resolved match, and follow-up action in one reviewable sequence. The delivery lesson: test the first consequential action after a success state, not only the celebration that precedes it.
While preparing DragSet, I used its QA scenario harness and mock service path to exercise the vehicle deck, match state, and race-challenge action without creating fake live accounts. It clarified a useful demo practice: label evidence as simulated, integrated, or operational. Simulated evidence proves repeatable UI behavior; integrated evidence checks a live dependency; operational evidence covers delivery and diagnostics. Naming the layer prevents a stable demo from being mistaken for backend proof.
NameSnap Picker ends with an ordered result rather than relying on the picker’s motion as the outcome. That gave the randomized interaction a concrete output structure: supplied names enter the flow, the selection runs, and a readable ranking marks completion. The milestone was not simply making an animation respond; it was making the result inspectable afterward. For randomized products, define valid output before styling how it arrives.