Critique App Blueprint — Student Portal with GPA Predictor (Flask + Tailwind)
Project Context
Hey team! My university group just built the MVP for an unofficial student dashboard portal using a Python/Flask backend and Tailwind CSS for the UI. The core feature is a 'GPA Predictor' where students input their current coursework grades, and the system runs a basic weight-calculation algorithm to predict their final semester grade. It stores user profiles using SQLite for now.
Feedback Requested
1. User Flow: After logging in, the user is redirected straight to the GPA input page. Should we show an overview dashboard first, or is it better to send them straight to the main feature? 2. Form Interaction: The grade inputs are numeric fields. Do you think dropdown selectors (A, B, C, etc.) would be faster to fill out than typing actual percentages? 3. State Management: Currently, if a user refreshes the page halfway through inputting grades, the session clears and they lose their data. How should I persist this temporary form data safely?
Critique Feed Thread
