I’m Bobby, an Android Dev and (still) an app hobbyist
Series of Article about Android Performance
These days, an app isn’t just about building features — it also needs proper logging (performance, analytics). The problem is, teams often don’t have a clear agreement on how to do it, which leads to confusion when debugging and makes the business logic messy with logging code.
When i stumbled upon the AOP Concept it might the proper framework to help implementing the logs, lets see whether this one can help
to fix the java 11 requirement, need to install java 11 first, and add the line below on root gradle.properties
then sync the project
org.gradle.java.home=/Library/Java/JavaVirtualMachines/temurin-11.jdk/Contents/Home
Interesting tools (approach)
git filter-branch
manually check git historyThree Phase in Compose
Compose can skip a phase entirely if nothing has changed in it
Prefer lambda modifiers when using frequently changing state, the video show case is using the scroll provider lambda over y property when performing translation, and reading the state inside the graphicsLayer
Since i often forget to about the name of the Version, the codename and the site is include the play store requirement changes, and major library info
Separate assert and code triggering into 2 different set of coroutine launch
UnconfinedTestDispatcher
Please note that when using flow the code triggering should still use a separate launch and not inside the test
block