maxonflutter / flutter_app_with_junior_ai Goto Github PK

We need to design the UI for the Notifications Screen, providing users with an organized, clear view of their notifications.

1. List Layout: Display notifications in a list format, with the most recent notifications at the top.
2. Notification Card: Each notification should be in a card format, displaying the message, time, and a relevant icon.
3. Read/Unread Indicator: Differentiate between read and unread notifications, possibly using color, font weight, or an icon.
4. Interactivity: Each notification card should have a clear touchable area. Include visual feedback (like a ripple effect) when a notification is tapped.
5. Action Buttons: Add a 'Mark as Read' button/icon and a 'Clear' button/icon for each notification. Also, include a 'Clear All' button at the top of the screen.

The app needs a dedicated API client to ensure seamless interaction with the backend. This API client will be crucial for managing product data.
Main objectives:

1. Create API Client: Build an API client that uses the appropriate HTTP methods (GET, POST, PUT, DELETE) for interacting with our RESTful backend.
2. Connect to Product Endpoints: The API client should interact with the following endpoints:
   • GET /products: Fetch all available products.
   • POST /products: Add new products.
   • PUT /products/{id}: Update details of a specific product.
   • DELETE /products/{id}: Remove a specific product.
3. Error Handling: Implement efficient error handling to manage potential issues during API communication.

The app needs a dedicated API client to ensure seamless interaction with the backend. This API client will be crucial for managing product data.
Main objectives:

1. Create API Client: Build an API client that uses the appropriate HTTP methods (GET, POST, PUT, DELETE) for interacting with our RESTful backend.
2. Connect to Product Endpoints: The API client should interact with the following endpoints:
   • GET /products: Fetch all available products.
   • POST /products: Add new products.
   • PUT /products/{id}: Update details of a specific product.
   • DELETE /products/{id}: Remove a specific product.
3. Error Handling: Implement efficient error handling to manage potential issues during API communication.

Our chat functionalities require a specific API client to facilitate interaction with our backend. This API client will be instrumental in handling chat and user data.
Main objectives:

1. Create API Client: Develop an API client that leverages suitable HTTP methods (GET, POST, PUT, DELETE) to communicate with our RESTful backend.
2. Connect to Chat and User Endpoints: The API client should interact with the following endpoints:
   • GET /chats: Retrieve all active chat conversations.
   • POST /chats: Start a new chat conversation.
   • GET /chats/{id}: Fetch a specific chat conversation.
   • GET /users: Retrieve all registered users.
   • GET /users/{id}: Fetch a specific user's details.
3. Error Handling: Implement robust error handling to manage potential problems during API

The product model should encapsulate:

1. Product Details: These details include basic properties that define a product.
2. Pricing: Each product should have a specified price attached to it.
3. Color Options: Products might come in different colors; this should be represented.
4. Description: A brief description that provides more information about the product.

To enhance our app's visual appeal and ensure uniformity, we need a vibrant fluo color scheme and specific styling for key widgets.

Fluo Color Scheme

Primary Color: #FF5C83 (Vibrant Pink)
Lighter variant: #FF8AB1
Darker variant: #FF2961
Secondary Color: #33FF57 (Neon Green)
Lighter variant: #66FF80
Darker variant: #00CC44
Error Color: #FF4343 (Bright Red)
Background Color: #FAFAFA (Soft Gray)

The app needs a standard styling for the following widgets:

FilledButton:

The button is dressed in a lively pink with soft gray text. On hover, this pink takes on a deeper tone. Sized comfortably, its rounded edges enhance its elegant look.

ElevatedButton:

Sporting a neon green hue, this button features crisp white text. It has a subtle lift when pressed, and its color intensifies on hover. Standard in size, its rounded corners complete its polished design.

AppBar:

The AppBar shines in a deeper shade of pink, paired with a pure white title. Its icons pop in a neon green, and a slight shadow graces its base, adding a touch of depth.

In order to ensure a secure user experience in our Flutter app, we require an Auth BLoC to handle user authentication effectively.

1. User Sign Up: The BLoC should support new user registration, validating user input and communicating with the backend to create a new user account.
2. User Sign In: The BLoC should facilitate user login by accepting user credentials, verifying them with the backend, and managing the user session.
3. User Sign Out: Users should be able to end their sessions securely. The BLoC should handle sign-out requests and properly terminate the user session.
4. Handle Errors: Implement comprehensive error handling to catch and address potential issues during the authentication process.

In order to ensure consistency and visual appeal across our app, we need to establish a Text Theme and Color Scheme.

Text Theme: Typography Guidelines

1. Font Family: A modern sans-serif font that is legible at all sizes.
2. Display:
   • Font size: Large and dominant for page titles.
   • Weight: Bold for emphasis.
   • Letter Spacing: Slightly spaced for readability.
3. Headline:
   • Font size: Moderately large for subheadings.
   • Weight: Slightly bolder than regular text, but less than Display.
   • Letter Spacing: Normal spacing.
4. Body:
   • Font size: Comfortable reading size for extended content.
   • Weight: Regular for standard content.
   • Letter Spacing: Regular spacing for ease of reading.
5. Caption:
   • Font size: Smaller than body text for auxiliary information.
   • Weight: Lighter than regular content.
   • Letter Spacing: Slightly increased spacing to offset smaller size.

Color Scheme

1. Primary Color: A vibrant shade that resonates with the brand identity.
   • Lighter variant: A muted version of the primary color for backgrounds or hover effects.
   • Darker variant: A deeper shade of the primary color for emphasis or depth.
2. Secondary Color: A contrasting color to the primary which complements it without overshadowing.
   • Lighter variant: A paler shade of the secondary color.
   • Darker variant: A richer tone of the secondary color for variation.
3. Error Color: A color that clearly signifies errors, preferably a shade of red.
4. Background Color: A neutral hue that complements the primary and secondary colors and offers a clean backdrop for content.

We need to design a new Profile Screen UI to provide users with a visually appealing and intuitive interface to view and edit their personal details.

1. Layout: The screen should have clearly defined sections for profile picture, personal details (e.g., name, email), and edit actions.
2. Profile Picture: Centrally position the user's profile picture with an option to change it. If no image is available, display a default avatar.
3. User Details: Display user details like name and email in an easily readable font size. Incorporate intuitive icons next to email and other details.
4. Edit Mode: On entering edit mode, fields should change to editable text boxes, with visible Save and Cancel buttons.
5. Feedback: On successful edits, visual feedback (like a brief color change or animation) should notify the user.

The cart model should be able to:

1. Add items to the cart: Users should be able to select a product and add it to their cart with a specified quantity.
2. Remove items from the cart: Users should have the option to remove items they've added to the cart.
3. Adjust item quantities: Users should be able to change the quantity of any item in their cart.
4. Calculate the subtotal: The model should automatically calculate the total cost of the items in the cart.

In our ongoing efforts to enhance user experience, we need a Form Validation Cubit to manage and validate user input effectively in our forms.

1. Input Monitoring: The Cubit should monitor form input fields and validate data as the user types.
2. Input Validation: The Cubit should use suitable validation rules for each form field, marking fields as invalid if they fail validation.
3. State Management: The Cubit should emit new states based on the validation results, enabling or disabling the form submission button as needed.
4. Error Handling: Proper error handling should be implemented to provide useful validation feedback to the user.

This project is about booking a flight ticket at national level,which will take all detail of passenger and payment method also.

Our Flutter app requires a dedicated BLoC for managing the various e-commerce categories effectively.

1. List all Categories: The BLoC should be able to fetch and handle a list of all current categories from our backend.
2. Category Selection: Users should be able to select a specific category and the BLoC should manage the state of this selection.
3. Update Category List: The BLoC should provide a mechanism to update the category list when new categories are added or existing ones are removed/updated in the backend.
4. Handle Errors: Proper error handling should be implemented to deal with any issues arising from API calls or data issues.

Our chat functionalities require a specific API client to facilitate interaction with our backend. This API client will be instrumental in handling chat and user data.
Main objectives:

1. Create API Client: Develop an API client that leverages suitable HTTP methods (GET, POST, PUT, DELETE) to communicate with our RESTful backend.
2. Connect to Chat and User Endpoints: The API client should interact with the following endpoints:
   • GET /chats: Retrieve all active chat conversations.
   • POST /chats: Start a new chat conversation.
   • GET /chats/{id}: Fetch a specific chat conversation.
   • GET /users: Retrieve all registered users.
   • GET /users/{id}: Fetch a specific user's details.
3. Error Handling: Implement robust error handling to manage potential problems during API

hi

We need a Data Filtering Cubit to handle states in cases where data needs to be filtered based on user preferences.

1. Data Fetching: The Cubit should fetch the necessary data from our backend.
2. Filter Application: The Cubit should apply filters based on user-selected criteria.
3. State Management: The Cubit should emit new states containing the filtered data, allowing the UI to rebuild with the updated data.
4. Error Handling: Any issues during the fetching or filtering processes should be appropriately handled and communicated to the user.