Feature Completion Status |% Completed

• Integrate Map API (Google Maps) |🟡 In Progress 70%
• Display User's Trip Destinations on Map|🟡 In Progress 60%
• Show Routes Between Destinations |🟡 In Progress 40%
• Backend Logic for Reminder Scheduling |🟡 In Progress 50%
• Push Notification Integration (Firebase Cloud Messaging) |🟡 In Progress 60%
• UI for Setting and Managing Reminders |🟡 In Progress 40%

Integrate Map API (Google Maps)

• Progress: Successfully integrated Google Maps API. Users' locations are being fetched and displayed on the map.
• Challenges: Some performance issues with larger itineraries.
• Next Steps: Fine-tune API interactions and ensure map rendering is smooth across devices.

Display User's Trip Destinations on Map

• Progress: Initial work completed. Destinations are correctly marked on the map.
• Challenges: Some UI elements related to destination markers need improvement.
• Next Steps: Optimize the display of multiple destinations and test for various user scenarios.

Show Routes Between Destinations

• Progress: Route visualization is in progress but not fully functional yet.
• Challenges: Accuracy of route calculations and rendering needs improvement.
• Next Steps: Complete and test the logic for route display and ensure routes are accurate.

Backend Logic for Reminder Scheduling

• Progress: Basic scheduling logic is implemented, allowing users to set reminders.
• Challenges: The logic for handling multiple reminders and time zones needs refinement.
• Next Steps: Improve recurring reminder functionality and test for different time zones.

Push Notification Integration (Firebase Cloud Messaging)

• Progress: Successfully integrated Firebase for basic notifications.
• Challenges: Testing for consistency and handling push notifications for multiple events is pending.
• Next Steps: Test end-to-end notification scenarios and ensure cross-device reliability.

UI for Setting and Managing Reminders

• Progress: The basic UI for setting reminders has been designed and partially developed.
• Challenges: User customization options (e.g., snoozing or recurring reminders) need to be implemented.
• Next Steps: Continue refining the UI and ensure a smooth user experience for reminder management.

Current Status:

AMBER The project is making progress, but certain features (such as user authentication with social media logins and destination search accuracy) are causing delays. The Map API integration is on track, but additional work is needed to refine both the route visualization and reminders system.

Team Goals for the Upcoming Week:

• User Registration and Login: Finalize and test with both email and social media authentication.
• Destination Search: Improve search filtering and suggestion accuracy.
• Itinerary Creation: Continue developing features to save and organize activities.
• Reminder System: Complete backend logic and test for scheduling and push notifications.
• Third-Party Booking: Begin initial work on this feature once other core features are stable.

Individual Team Member Status:

Panwala Deep:

• Focused on the user authentication system, completed email-based login. Set up the basic DevOps pipeline.
• Next Week: Finalize social media login integration and troubleshoot DevOps issues.

Pavan Rohith Midimilla:

• Tested and validated the user login feature.
• Next Week: Finalize login testing and prepare test cases for the destination search feature.

Nanda Eswar Vimal Boppudi:

• Worked on destination search filters and data flow.
• Next Week: Focus on search accuracy and integrate location-based filters.

Hitesh Naval:

• Developed the basic UI and data structure for itinerary creation.
• Next Week: Expand the itinerary feature to organize activities by day.

Purvesh Kapadiya:

• Designed the UI for the itinerary and destination search screens.
• Next Week: Continue refining the design and ensure a smooth UI/UX flow.

Team Activities: Sprint Planning Meeting: 10/16/2024 (All members). Pair Programming: Destination Search API setup on 10/18/2024 (Nanda and Hitesh). Frontend Design Review Meeting: 10/19/2024 (Purvesh, Pavan).

Team Decisions: Third-Party Booking Integration: Deferred to the next sprint to focus on stabilizing core features. Email vs. Social Media Login: Prioritizing email-based login to ensure a functional core login system before adding social media options.

Other Comments: We are slightly behind schedule for Sprint 2, but confident that catching up is possible once the authentication and search accuracy issues are resolved. No major changes to the scope or requirements have been introduced.