t-matzm0/travelet_flutter

AI Summary: Implement user authentication and profile management features using Firebase Auth for the Travelet Flutter app. This includes login/logout functionality, user registration, and profile information management (nickname, profile/banner images, bio, and social media links). The task requires ensuring persistent login sessions and implementing a profile screen. Existing Firebase Auth setup is assumed.

AI Summary: Enhance the existing travel spot search functionality by adding location-based search, tag search, budget range search, user search, and time-limited search from a specified location. Implement filtering by category and tag, sorting by popularity and date, and saving search criteria. This requires backend integration with the search screen, improvements to the display of search results, and the implementation of filtering features. The task is related to an existing plan creation feature and uses the current search screen UI.

AI Summary: Integrate the Google Maps API into the Travelet Flutter app to display spot locations on a map, visualize routes between planned itinerary points, allow users to search and select locations, and potentially show routes based on different transport modes. This requires using the `google_maps_flutter` package and integrating with existing data models (Spot, Itinerary, TransportMode).

AI Summary: Migrate the sample travel planning app data to Firestore, implementing persistent storage for user data, spot data, and itinerary data. This includes ensuring real-time synchronization, applying Firestore security rules, and handling offline capabilities. Sample data should be removed after migration.

AI Summary: Implement a travel plan creation feature allowing users to create, edit, and post travel plans. This includes a UI for plan creation, spot selection and ordering, accommodation flags, tagging, and Firestore data persistence. The feature should also include plan naming, waypoint registration, accommodation flagging, custom tagging, and public/private settings. Acceptance criteria include implementing a "Prepare" FAB, displaying created plans, and a plan details screen. This task depends on the authentication feature (Issue #2) and the design concept.