Product Feedback — StudyPilot AI
1. Vercel
What I used it for: Hosting and deploying the StudyPilot AI web application so judges can access it through a public URL.
What worked well: Deployment was straightforward, and Vercel provided a live URL and deployment status, making it easy to publish updates.
What needs improvement: Build and runtime troubleshooting could provide clearer, more actionable explanations for beginners. Preview and production deployment management could also be easier to understand.
Onboarding experience: The GitHub integration and deployment workflow made it relatively easy to get started.
Would I use it again? Yes. I would use Vercel again for rapid deployment, preview links, and hosting frontend projects.
2. GitHub
What I used it for: Hosting the public source code, tracking changes, maintaining project documentation, and providing access to the project for reviewers.
What worked well: GitHub made it easy to maintain version history, update the README, and keep the source code publicly accessible.
What needs improvement: Merge conflicts, repository configuration, and deployment-related debugging can be challenging for new developers.
Onboarding experience: Creating a repository and pushing changes was manageable, although understanding branches, commits, and deployment integrations required some learning.
Would I use it again? Yes. GitHub is useful for version control, collaboration, open-source projects, and sharing code with judges.
3. Browser APIs — Web Speech API
What I used it for: Adding optional browser-based speech recognition for voice input and speech synthesis for spoken assistant responses.
What worked well: These built-in browser capabilities provide a way to experiment with voice interaction without requiring a separate speech API key.
What needs improvement: Speech recognition support and behavior vary by browser and device. Permission handling, recognition accuracy, and clear fallback behavior need careful testing.
Onboarding experience: Getting started is relatively simple because the APIs are built into supported browsers, but browser compatibility and permission behavior require attention.
Would I use it again? Yes, for browser-based prototypes and accessibility experiments, with text input as a fallback.
4. HTML, CSS, and JavaScript
What I used them for: Building the responsive dashboard, task and study-plan management, focus timer, flashcards, progress tracking, local data persistence, and assistant interactions.
What worked well: These technologies allowed me to build and iterate on the application without requiring a complex framework or separate backend.
What needs improvement: As the project grows, separating application logic into smaller modules and adding more automated tests would improve maintainability and reliability.
Onboarding experience: The browser-based development workflow made it easy to get started and see changes quickly, while debugging interactive features required practice.
Would I use them again? Yes. They are a strong foundation for lightweight, responsive web applications and rapid prototyping.
Overall feedback
This project helped me explore the full workflow from implementation and version control to deployment and browser-based voice interaction. The biggest improvement areas are cross-browser testing, automated testing, and making the assistant more capable. StudyPilot AI currently uses built-in intent matching rather than a live generative AI backend, and its voice features depend on browser support.
Log in or sign up for Devpost to join the conversation.