Some Best Practices

[machadaCosta]

In brief, rating criteria are based on best practices.

Project Best Practices:

• [ ] Readme
  • [x] Required Contributors, Desc. of the app
  • [x] Screenshots of the final app
  • [ ] Sources and References (API link)
• [ ] Relevance of commits on GIT ("two commits is better than one")
• [ ] Relevance of GIT Flow (branches)
• [ ] Respect of the return date, Follow-up
• [ ] Originality, consistency of the project

Kotlin Android Best Practices:

• [ ] relevance of the navigation system put in place (Menus)
• [ ] graphical interface
  • [ ] use of layouts (one layout, the ConstraintLayout, 2 layouts maximum for one screen, combination of two LinearLayout)
  • [ ] use of cards, alert dialog and other Material Design items (cf. Basic UI)
• [ ] use of the ViewBinding
• [ ] use of resources to externalize strings /!\ hard-coded strings
• [ ] consistency in the naming of classes and variables
• [ ] code indentation, use of package, comment, beware of unused variables or parts of code
• [ ] use of the elements "seen" during the sessions
  • [ ] ConstraintLayout, or no layout if it's not needed
  • [ ] CustomView if it's relevant to play with...
  • [ ] Kotlin concepts (array, lateinit, inline fun, with(), when(), also, etc.)
  • [ ] App class
  • [ ] Gradle variables

Bonus

• [ ] display a list of items with a RecyclerView (cf. Afficher une liste d'élément)
• [ ] SharedPreference for light data or Room library for data persistence (or SQLLiteOpenHelper)
• [ ] Retrofit library for network communication with a third party

References

• Clean Code - Robert C. Martin
• Example de convention de nommage, à attacher à votre projet

“If you think you are too small to make a difference, try sleeping with a mosquito.” ― The Dalai Lama

[machadaCosta]

To fix:

• minSDK has to be less than 21 Reference: developer.android.com: Android Basics in Kotlin