Efficient Delivery App Developed with FlutterFlow & Firebase

Efficient Delivery App Developed with FlutterFlow & FirebaseEfficient Delivery App Developed with FlutterFlow & Firebase

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

Chanlika SERVAIS

pro

• Mar 7

Developed a package delivery mobile app using FlutterFlow and Firebase. The app allows users to request deliveries from point A to point B, with a single platform for both clients and drivers and real-time delivery tracking using maps.

Flutterflow Development Firebase Project Management FlutterFlow

Florencio Rosales

• Mar 18

sounds good

Chanlika SERVAIS

pro

• Mar 18

It was very challenging ^^ especially the Senegal payment method

Ishan Lakhani

pro

• Oct 30

Introducing QuickBite, a food delivery app designed to make ordering food simple and enjoyable! 🍔

Focused on clean visuals, intuitive navigation, and a smooth food ordering experience.

I'd love to hear your thoughts! Feel free to share your feedback or suggestions in the comments. Your input will help me improve my future designs.

Check it out and let me know what you think in the comments! 🚀

ChatGPT Figma Mobile Design

Dan Caetano

• Oct 31

Looks really cool

Zahid Hussain

pro

• Oct 29

From packed boxes to a shipment the client can track.

This TechFoundry IMS demo reuses box details, retrieves UPS rates, creates shipping labels, and keeps tracking connected to the client order. A practical example of the AI and automation workflows we build into business software.

Watch the client shipping demo: https://www.youtube.com/watch?v=8ohniU08JAA

#AI #Automation #SoftwareDevelopment #Shipping

Yonatan Tesfaye

pro

• Oct 30

I like that the shipment stays tied to the client order instead of living in a separate carrier tab. When box details get edited after the UPS rate is retrieved, does the system re-quote before creating the label, or lock the original rate? I'd be curious how you handle that mismatch on the tracking side.