-
Notifications
You must be signed in to change notification settings - Fork 0
Implementation Plan
This implementation plan divides development into 4 milestones:
- MVP - Demo Review – Pre-MVP time slot reserved for testing and bug fixing
- MVP (Minimum Viable Product) – Core posting and map exploration
- Intermediate Milestone – Interaction, recording, and discovery features
- Final Milestone – Transcription, discovery improvements, and authentication enhancements
A short milestone reserved for reviewing the testing status before MVP — used to find and fix bugs so the MVP demo is stable.
Deliver the core historical story sharing workflow:
User registers → uploads media → pins story to map → others view it.
This milestone validates the basic idea of the platform.
Users can create accounts using:
- username
- password
Users can log in with their registered email and password.
Users can upload media from their device gallery:
- photos
- videos
- audio
Users can create story posts that include:
- uploaded media
- textual description
- location metadata
- historical date
Users can submit the post after completing necessary fields and see a success confirmation.
Stories appear on an interactive map using their coordinates.
Map features include:
- map navigation
- markers for stories
- viewing story details
- zoom in/out controls
- Design initial database schema:
- users
- stories
- media files
- comments
- likes
- saves
- Implement authentication APIs
- Implement story creation API
- Implement story retrieval API
- Store media files in cloud
- Implement geolocation storage for stories
- Implement basic search queries
- Write unit tests for critical APIs
- Document API endpoints
- Create responsive UI layout
- Implement registration and login pages
- Implement story creation interface
- Implement media upload interface
- Implement interactive map view
- Implement story detail page
- Implement basic navigation and UI styling
- Connect frontend to backend APIs
- Structure repository (frontend / backend)
- Create Dockerfiles
- Configure docker-compose
- Configure CI pipeline
- Set up database environment
- Configure media storage
- Deploy staging environment
- Manage environment variables
- Deployable web application
- User authentication system
- Media upload functionality
- Story creation with location and time
- Interactive map displaying stories
- Basic search functionality
- Containerized deployment
- CI/CD pipeline
- API documentation
Improve the platform with interaction features and location-based discovery.
Users can:
- like stories
- comment on stories
- save stories
Users can record media directly inside the application:
- audio recording
- video recording
Users can discover stories close to their location.
The system:
- retrieves nearby stories
- displays them on the map
Users can report stories.
Admins can:
- review reports
- remove inappropriate content
- Implement like / comment / save APIs
- Implement geospatial queries for nearby stories
- Implement recording upload endpoints
- Implement reporting endpoints
- Implement admin moderation APIs
- Improve search queries
- Add notification triggers for interactions
- Implement like / comment UI components
- Implement saved stories view
- Implement recording interface
- Implement "stories near me" map interaction
- Implement reporting interface
- Implement moderation interface for admins
- Extend CI pipeline with integration tests
- Configure media storage for recorded content
- Improve deployment pipeline
- Monitor server performance
- Interaction features (likes, comments, saves)
- In-app media recording
- Stories near me functionality
- Reporting and moderation system
- Improved backend APIs
- Updated documentation
Deliver a complete and production-ready platform with advanced discovery and authentication features.
Audio recordings are automatically transcribed.
Users can filter stories using:
- location
- date
- media type
- keywords
Users have dashboards showing:
- their stories
- saved stories
- engagement statistics
Users receive badges for contributions.
Example:
- First story badge
Users can authenticate with Google.
System suggests usernames during registration.
- Integrate speech-to-text service
- Implement transcription pipeline
- Implement advanced filtering queries
- Implement dashboard statistics APIs
- Implement badge logic
- Integrate Google authentication
- Optimize database queries
- Perform load testing
- Implement transcription review UI
- Implement advanced filtering interface
- Implement user dashboard
- Display badges on profiles
- Implement Google login UI
- Improve overall UI/UX
- Configure external transcription service
- Scale infrastructure for media processing
- Configure caching
- Implement monitoring tools
- Harden security configuration
- Deploy production environment
- Automatic audio transcription
- Advanced story filtering
- User dashboards
- Badge system
- Google authentication
- Optimized infrastructure
- Production-ready deployment
- Final documentation and wiki updates
Team Members
- Lab 1 Report (12/02/2026)
- Lab 2 Report (19/02/2026)
- Lab 3 Report (26/02/2026)
- Lab 4 Report (05/03/2026)
- Lab 5 Report (12/03/2026)
- Lab 6 Report (26/03/2026)
- Lab 7 Report (02/04/2026)
- Lab 8 Report (16/04/2026)
- Lab 9 Report (30/04/2026)
- Lab 10 Report (07/05/2026)
- Weekly Meeting 1 (14.02.2026)
- Weekly Meeting 2 (21.02.2026)
- Weekly Meeting 3 (28.02.2026)
- Weekly Meeting 4 (07.03.2026)
- Weekly Meeting 5 (14.03.2026)
- Weekly Meeting 6 (19.03.2026)
- Weekly Meeting 7 (28.03.2026)
- Weekly Meeting 8 (05.04.2026)
- Weekly Meeting 9 (11.04.2026)
- Weekly Meeting 10 (18.04.2026)
- Weekly Meeting 11 (02.05.2026)
- Weekly Meeting 12 (09.05.2026)
- Customer Meeting 1 (18.02.2026)
- Stakeholder Meeting 1 (09.03.2026)
- Milestone Review Meeting (05.04.2026)
- MVP Test Meeting (08.04.2026)
- Customer Meeting 2 (30.04.2026)