Open Issues Need Help
View All on GitHubWhat we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
What we can do, is all we can do
AI Summary: Implement a "Discovery page" featuring a "Shelter" cause tile with a carousel of related support items. This involves creating a reusable `CauseTile` component, fetching and displaying item data (potentially mocked for MVP), implementing like/unlike functionality using Firebase (or a mock), and handling navigation to a dedicated item list page. The implementation should follow the existing MVVM architecture and Provider state management of the project.
What we can do, is all we can do
AI Summary: Implement a "Discovery page" featuring a charity card with an image, organization name, description, like button, and like count. This card should also include a carousel showcasing associated items with images, names, and like counts. The like button functionality should persist user likes using Firebase, and a "See All" button should navigate to a dedicated item listing page. The implementation should follow the existing MVVM architecture, Provider state management, and project styling guidelines. Responsive design is crucial.
What we can do, is all we can do
AI Summary: Implement a delivery option selection feature on the checkout page. This involves creating reusable UI components for 'Shop to pick up point' and 'Ship to Home' options, ensuring the selected option is visually highlighted according to the provided design, and adhering to the project's MVVM architecture, Provider state management, and coding standards. The implementation should be consistent with the existing login feature's structure.
What we can do, is all we can do
AI Summary: Implement a shipping address feature for a Flutter app using the MVVM architecture and Provider for state management. The feature should include an address search functionality using the Google Maps Places API (either directly or via a package like `google_places_flutter` or `google_places_autocomplete_text_field`), allowing users to select pre-populated addresses from a dropdown. The implementation should adhere to the project's existing architecture and coding standards, including using the core utilities and avoiding relative imports.
What we can do, is all we can do
AI Summary: Implement a payment selection screen in a Flutter app using the existing MVVM architecture and Provider state management. The screen should display options for Card, Apple Pay, and Google Pay, and navigate from the checkout page. The implementation should follow the project's established coding style and structure, utilizing existing core components and adhering to best practices outlined in the project documentation.
What we can do, is all we can do
AI Summary: Implement the 'Complete Order' functionality within the CherryMVP Flutter application. This involves handling successful and unsuccessful order completion scenarios, displaying appropriate success and error screens according to provided designs, and integrating with existing payment and address selection features. The implementation should adhere to the project's MVVM architecture, Provider state management, and established coding standards.
What we can do, is all we can do
AI Summary: Implement a pick-up point selection feature in the CherryMVP Flutter app. This involves creating a dropdown that displays the three nearest pick-up locations (requiring integration with an external provider, yet to be determined). The selected location should be displayed, and the implementation should follow the existing MVVM architecture and Provider state management of the project. UI design is provided.
What we can do, is all we can do