NatanAmorim / curie_app

(Pre-Alpha) Open-source app created to be my template and feature playground, made with Flutter.

Curie (Pre-Alpha)

Concept

About

It's FREE -> "Free as in freedom"

License

• Copyright 2022 Natan Amorim Moraes

Licensed under the GNU General Public License, Version 2.0 (the "License"); you may not use this app except in compliance with the License.

You may obtain a copy of the License at GPL-2.0 license.

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

See the License for the specific language governing permissions and limitations under the License.

Versioning

• This project implements an opinionated interpretation of Calendar Versioning.

                                             + YEAR
                                             |
        + YEAR                               |  + MONTH OF THE YEAR
        |                                    |  |
        |  + MONTH OF THE YEAR               |  | + RELEASE ITERATION
        |  |                                 |  | |
        |  | + RELEASE ITERATION             |  | |   + RELEASE CANDIDATE ITERATION
        |  | |                               |  | |   |
     2022.03.2                            2022.03.3-rc1

     ^ RELEASE                            ^ RELEASE CANDIDATES

TODO

Some of the things needed for release.

• Implement Theme switcher.
• Implement Language switcher.
• Implement State Managament and Dependecy injection with Riverpod.
• Implement Routing with GoRouter.
• Implement API with DIO and cancelation token.
• Connect with Curie Api.
• Make Responsive to fit all screen sizes.
• Implement DDD file Structure.

Pull Request

• Clearly describe what you aim to add or fix.
• Try to minimize code changes and use existing style/functions.

Reporting Issues and Bugs

To better respond to issues please follow these general guidelines when explaining the problem.

1. Clearly describe what you aim to fix, if relevant attach output/logs/screenshots.
2. Describe how developers can reproduce the bug.