client_projects
/
mobile-best-practice
4
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

move wip mbp into a wip file

fde/add-new-mbp
DEMEY Fanny 2024-04-03 20:59:57 +02:00
parent 1b2a1c72c7
commit f823e5d24f
1 changed files with 36 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

36
chapters/MBP_WIP_fr.md Normal file
View File

@ -0,0 +1,36 @@
* // TODO : à écrire
// Don't access the Android UI toolkit from outside the UI thread. => risque de fuite mémoire (la vue est détruite avant que le traitement se termine, la référence a cet objet est maintenu)
// Limiter l'utilisation des Service (https://developer.android.com/topic/performance/memory#Services)
// Préférer l'utilisation de SparseArray, SparseBooleanArray, et LongSparseArray plutôt que `HashMap` (https://developer.android.com/topic/performance/memory#DataContainers)
// Abstraction à éviter si peu utile - https://developer.android.com/topic/performance/memory#Abstractions
// A creuser : https://developer.android.com/topic/performance/memory#Abstractions
// Notifications
// ABI ??
// Feature play store
// Utiliser correctement implementation testImplementation debugImplementation pour ne pas packager des librairies utilisées uniquement pour les tests ou le debug
// Reduce cost of inflation (ex ConstraintLayout instead of nested LinearLayout) https://developer.android.com/topic/performance/vitals/render#recyclerview_too_much_inflation_or_create_is_taking_too_long If your view types look good, look at reducing the cost of your inflation. Reducing unnecessary container and structural views can help. Consider building itemViews with ConstraintLayout, which can help reduce structural views.
* Monitorer la taille de l'application dans le temps (ex d'outil : https://github.com/JakeWharton/diffuse + le playstore)
* Reduire la taille de l'application : https://engineering.atspotify.com/2023/11/the-what-why-and-how-of-mastering-app-size/ https://medium.com/googleplaydev/shrinking-apks-growing-installs-5d3fcba23ce2
* [Limiter le recours aux canvas](/chapters/BP_4013_fr.md)
* [Coroutines / Scope / Lifecycle / annulation de traitement](/chapters/BP_4032_fr.md) // https://developer.android.com/topic/libraries/architecture/coroutines
* https://developer.android.com/kotlin/coroutines
* https://developer.android.com/kotlin/coroutines/coroutines-adv#main-safety
* [Préférer la pagination au défilement infini](/chapters/BP_4035_fr.md)
* Ne pas effectuer de traitements asynchrones conséquents sur le thread principal (Dispatcher.MAIN avec les coroutines)
Avoid delivering all of your assets and resources at install time if they aren't needed immediately. Reduce your app's install size by placing the largest files in dynamic feature module(s) and delivering them conditionally or on demand, or consider alternatives such as streaming media files. Learn more