Spring Boot Backend & Admin Panel
Budget: ₹1,500 – ₹12,500 INR
My kids’ book-reading app is already live on Google Play, but its current backend has hit its limits. I now need a complete Spring Boot rebuild that is secure, scalable and easy to maintain.
Core requirements
• Robust user authentication and role-based authorisation
• A flexible content management flow that lets me upload, edit and order stories, poems and chapters without touching code
• Built-in analytics and reporting so I can track active readers, session length and popular titles
• Full chapter management for every book, including draft → publish states
What I expect as final deliverables
1. RESTful Spring Boot API with clean, versioned endpoints
2. A responsive admin panel (your choice of React, Angular, or Thymeleaf) tightly coupled to the API
3. Secure data layer (JPA/Hibernate with PostgreSQL or a data store you can justify)
4. Docker-ready deployment scripts plus basic CI/CD instructions
5. Clear README and endpoint documentation that my mobile team can plug into immediately
I’m open to your architectural suggestions—microservices, monolith, or hybrid—so long as they keep hosting costs sane while giving us room to grow. If you have previous work with children’s content or media-rich apps, point me to it and tell me how you handled scale and security.
Looking forward to seeing how you would structure the solution and timeline.
Core requirements
• Robust user authentication and role-based authorisation
• A flexible content management flow that lets me upload, edit and order stories, poems and chapters without touching code
• Built-in analytics and reporting so I can track active readers, session length and popular titles
• Full chapter management for every book, including draft → publish states
What I expect as final deliverables
1. RESTful Spring Boot API with clean, versioned endpoints
2. A responsive admin panel (your choice of React, Angular, or Thymeleaf) tightly coupled to the API
3. Secure data layer (JPA/Hibernate with PostgreSQL or a data store you can justify)
4. Docker-ready deployment scripts plus basic CI/CD instructions
5. Clear README and endpoint documentation that my mobile team can plug into immediately
I’m open to your architectural suggestions—microservices, monolith, or hybrid—so long as they keep hosting costs sane while giving us room to grow. If you have previous work with children’s content or media-rich apps, point me to it and tell me how you handled scale and security.
Looking forward to seeing how you would structure the solution and timeline.