Back to portfolio

Project journal

Mobile Application

Picky, a Flutter food-sharing application prototype that I developed myself, connecting account flows, location-aware posts, Firestore data, and mobile navigation.

Illustrated mobile screens and a food-sharing post for the Picky application.
Editorial project cover
Where
Mahidol University · ITDS283
Project period
Submitted April 2025
My role
Sole application developer
FlutterDartFirebaseFirestore
View source on GitHubView Figma design

Turning the food-sharing idea into an application

I developed Picky myself for the Mobile Application project. The idea was to create an application for sharing surplus food, giving users an account, a way to create a post, a feed to browse, and a detail page to understand what is being offered.

My work covered the application implementation across those screens and the data behind them. The GitHub repository and Figma file are linked here so the implementation and design material can be explored together.

Inside the prototype

Original simulator screenshots from my April 2025 course report: signing in, browsing the feed, and creating a post. Names and ratings shown in the feed are example interface content.

Picky sign-in screen with empty email and password fields, a Sign Up link, and a Login button.View full size ↗
Sign in to a Picky account.
Picky home screen showing nearby food entries, a list of sample posts, and an add button.View full size ↗
Browse the food-sharing feed.
Picky post form with title, description, image URL, rating, and Submit fields.View full size ↗
Enter the details for a new post.

Connecting screens with persisted information

The implementation uses Flutter and Dart, Firebase Authentication for accounts, and Firestore for posts. The add-item screen obtains location information and saves a post with its details and coordinates. The home screen reads posts and connects the feed with a detail screen.

That gives the interface a data flow to work around: information is entered, persisted, retrieved, and opened again. Sign-in, loading, navigation, returning from the posting screen, and signing out are part of the surrounding application behavior.

A post's path through Picky

  1. Create

    Enter the post details and obtain location information.

  2. Store & retrieve

    Persist the post in Firestore and load it for the feed.

  3. Explore

    Navigate from an item in the feed to its details.

The posting and browsing path in the application prototype.

Planning how the screens connect

The original user-flow diagram from the course report maps the intended experience, including planned chat, notification, and reservation paths. It describes the design scope; those paths are not all complete in the prototype.

Picky user-flow diagram connecting login and registration with the home feed, post creation, item details, chat, notifications, and profile screens.View full size ↗
Original navigation and feature planning. Open the full-size image to read the diagram.

What the prototype helped me work through

Building the application myself connected the visible interface with authentication, stored data, location, and navigation. It gave me a practical example of how a change in one screen affects the information another screen needs.

The course report records checks for account flows, profile changes, post creation, detail navigation, and signing out. It also lists further work, including real-time chat, the complete reservation handoff, and reward-related features. The implementation presented here remains a prototype, with those larger service flows as areas for development.