Hey everyone! I'm currently working on a portfolio project that I hope will impress potential employers. The idea is to create a real-time asset tracking and management system, kind of like a simplified logistics platform. There are three main roles in my project: Clients (who can view live asset locations on a web app), Operators (who manage assets and schedules through an admin dashboard), and Field Agents (who use a mobile app to share their GPS locations).
My tech stack includes Next.js for both the UI and backend, Supabase for the database and authentication, Pusher for real-time updates, and Leaflet for mapping. The data flow involves my mobile app sending GPS coordinates to a Next.js API, which triggers updates on the client dashboard in real-time. I've implemented Row Level Security in Supabase to enhance security.
So far, I've completed the authentication and authorization flow for the web app and am making solid progress on the UI and proof-of-concept for the live map updates.
I'd love to know your opinions! 1) On a scale of 1-10, how impressive do you find this project for a student portfolio? 2) Are there any flaws in my approach (Next.js API -> Pusher -> Client)? 3) Does this reflect good skills for a full-stack or frontend role? I'm aware that asset tracking is a generic idea, but I'm focused more on showcasing solid engineering practices than on originality. Any feedback or insights are welcome! Thanks for taking the time to read this!
3 Answers
Your concept is solid! It's pretty much how many delivery apps like Uber and Foodora function. Just make sure to incorporate visuals like gifs or images in your project presentation for job applications. Employers don't want to wade through text; they prefer quick, engaging highlights accompanied by visuals.
This project sounds like an impressive MVP! It showcases your ability to work with a full stack and get a project to a usable state. Just remember that hiring managers won't dive deep into your code – they’ll want to discuss your technical knowledge, like how you handled web sockets or dealt with challenges during development. Use the project as a conversation starter, and highlight your problem-solving skills and any design patterns you implemented. Also, be prepared to clarify how much of it was your work versus templates or AI-generated content. And just a tip: when you say "asset tracking," be specific about the type of assets – mentioning it's for delivery services might help clarify your focus.
That makes sense! Just so you know, when I say 'asset tracking,' I'm thinking delivery services like Zomato or Uber, so that context could help.
Honestly, this looks like a solid portfolio piece! I'd rate it around an 8 out of 10 for a student project since it covers authentication, real-time data, security with RLS, and frontend mapping. The flow you’ve built (Next.js API -> Pusher -> Client) is standard and effective. The main downside is that asset tracking is a common idea, but that's not a dealbreaker since most hiring managers prioritize clean code and good architecture over uniqueness. You're definitely on the right track!
Totally get that... I struggled a bit to come up with a unique idea!
But won't that come off as too informal?