Quice, the application that tells you what to eat.

---

---

Quice is an Android and iOS application that tells you what you should eat by analyzing many data like your physical activity, your morphology and others...

You will find here how to contribute to Quice.

Repositories

• Quice-App: not yet created
• Quice-API: not yet created
• Quice-UIUX: https://github.com/Quice/Quice-UIUX
• Quice-Logo: https://github.com/Quice/Quice-Logo

Technologies used

Here is a list of the technologies we use:

Because we want to be a young project, which uses the next-gen technologies, we will use these technologies:

• For the application, Flutter → https://github.com/flutter/flutter

  Flutter is the future of Mobile App Development. The feature that convinced us the most is the creation of cross-platform applications based on a single code base.

  You can know more about why we chose Flutter by reading this article.

• For the backend, Go → https://github.com/golang/go

  Go is a recent popular language. It is fast, powerful, and has a super community.

  Go is a super language for the backend. It is one of the simplest languages, it compiles lightning-quick into fast native code and has excellent support for concurrency with goroutines and channels.

• For the machine learning and data science part, Julia → https://github.com/JuliaLang/julia

  Julia is a very recent language which is very promising. It is a very fast language, which has a lot of data science and machine learning integrations.

• For the database, MariaDB → https://github.com/MariaDB/

  MariaDB is a reference in the RDBMS. It provides the best rapidity for the less of resources. That's why we chose it.

Best Practices

Here a list of the internal Best Practices we use:

• Best Practices for Flutter
• Best Practices for Dart
• Best Practices for Go
• Best Practices for Julia
• Best Practices for MariaDB
• Best Practices for commit messages (Emoji commit messages)
• Best Practices for REST API

Formatting

To keep the project clean and readable, each file should be commited following the formatting of the .prettierrc file. Of course, you are free to format the code as you want when you are editing it.

The .prettierrc file will be in all repository.

---

The above information may not be specific enough to know how to contribute. For more information about the project, you can find a CONTRIBUTING.md file in each repository

---

Contributors ✨

Thanks goes to these wonderful people (emoji key):

Arthur Fontaine 💻

This project follows the all-contributors specification. Contributions of any kind welcome!