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
Each stock adjustment should get its ID when the person taps Confirm and keep it through every retry, because the Firestore transaction recognizes a repeated write only by finding that ID already recorded.
duskolicanin.com
Build a Flutter QR Inventory Scanner Without Duplicates
Stop duplicate stock entries from a Flutter QR scanner: lock detections until the user confirms, validate the payload, and retry Firestore writes with one ID.
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
One walk through Pasadena. Two ways to design it.
A: Field Guide, with the map up front.
B: Departure Board, with the itinerary up front.
Same places, same features. Which would you choose: A or B?
Download the Flutter source code for both versions for free.
https://contra.com/products/7ySCJSxh-switchback-two-flutter-app-designs
4 voted
50%
4 voted
50%
8 votes
Closed
Map up front for me. When I'm walking a new city I want to see where things are before the schedule. Cool that you shared the Flutter source!
I removed 2 steps from a café's booking flow. Bookings went up 30%.
No new features. Just three changes:
Cut every step that isn't the booking. Creating an account can wait until after someone has booked.
Show the price from the first screen. A total that only appears at the last step feels like a trick, even when it isn't.
Confirm instantly. A spinner right at the moment someone commits is where doubt creeps in.
The booking didn't need more. It needed fewer reasons to stop.
How many steps does your booking or checkout take right now?
Showing transparent pricing upfront and removing unnecessary steps makes it easier for customers to complete their bookings with confidence.
Giving an AI access to your store data is lowkey terrifying. So the website’s whole job here is making that part feel safe.
Card explorations for the trust section, wip:
→ Pick what it sees
→ See every lookup
→ Turn it off anytime
Went orange only on the middle one. The log is the proof, the other two are just controls.
Which one hits first for you?
