// the take
A university mobile programming course project — a Flutter e-commerce app for a cosmetics store with customer and admin roles. Uses PocketBase for auth and product/order data, SQLite for the local cart. Aimed at Flutter learners wanting a complete-but-simple CRUD example with role separation.
Split-backend approach (PocketBase for server state, SQLite for offline cart) is pedagogically sound and shows the student understood why local state needs separate storage. Role-based UI separation (customer vs admin screens) is cleanly scoped per contributor, making the code structure easy to follow for course review. PocketBase was a reasonable choice here — it handles auth, file uploads for product images, and real-time updates without needing a custom backend.
The `.env` file is committed to the repo — credentials are likely in version control, which is an immediate disqualifier for anything beyond local demo use. Zero stars and a course-project README mean this has no community validation and will likely go unmaintained after the semester ends. The product schema stores `isFavorite` as a field on the product itself rather than per-user, meaning one user's favorites affect everyone's view. The directory tree is mostly Android build artifacts that should be gitignored, suggesting git hygiene wasn't part of the curriculum.
We read the README, the directory tree and a key source file in June 2026. Nobody pays to be listed. How we judge →