A Flutter app where users spend their NuConta balance on awesome products.

The project was written in Flutter/Dart so it can be run having Flutter/Dart installed on your machine and running "flutter run".

Everyone knows that BLoC is one of the favorites flutter patterns and it is widely used by the industry. I tried to write the solution as simples as possible. Taking this into account, there was no need to manually manage state between different widgets and that is the reason why I prefer not to use BLoCs in this project. I have chosen to use the default GraphQLProvider and their Query Widget which already deals with exception and loading handling.

I have written a bloc (marketplace_bloc), but in the end, I choose not to use it because of these simplicity reasons.

graphql -> Client, Queries and Mutation for GraphQL requests. models -> data models.
pages -> all the screens.
services -> API communication.
utils -> useful functions/classes.
widgets -> individual widgets used for building the pages.

test -> unit and widget tests
test_driver -> integration tests

I tried to divide everything I could into individual widgets and put these individual widgets in the "widgets" folder. For example, you can see a Widget that receives a Customer object and build its customer balance and info.