View profile

“We all have dreams. But in order to make dreams come into reality, it takes an awful lot of determination, dedication, self-discipline and effort.”

StoicallyTyped Newsletter
Hey! I know I’m a day late, but better late than never right? Well, even never is sometimes okay too. You gotta take care of yourself, ya know?
Lets get to the goods. 🏂

👾 Fun Stuff
Did you know visiting the site https://log.wtf redirects to the r/mAndroidDev subreddit?
📚 TL;DRs
Library Upgrade!
Some fun libraries from Google got new versions last week! Here’s the changes:
There’s also an updated Codelab for Jetpack WindowManager!
👥 Community Content
Don’t get stung by OWASP: An intro into writing code for greater Android Security with Ed George
Don’t get stung by OWASP: An intro into writing code for greater Android Security with Ed George
High performance with idiomatic Kotlin
🎙 Upcoming Talks
This week we will be joined by Maru Ahues Bouza for the Android Dev Twitter Space! Set a reminder by clicking the image below.
Click to set a reminder and join us on Friday!
Click to set a reminder and join us on Friday!
🟣 Twitter Space Recap
Android Dev Hang: GDE Feminati Panel Discussion.
Matt McKenna
Thank you to everyone who stopped by today's #AndroidDev Space!

Here's all of the resources that were mentioned!

👇
⭐️ Answer to Last Week's Question
Last week I asked you about the coroutine scopes in Kotlin and when are they best used?
There are three main coroutine scopes available to use.
  1. GlobalScope
  2. LifecycleScope
  3. ViewModelScope
GlobalScope is a delicate API to use. It can have pretty severe consequences if used improperly. It is not bound to any job and is recommended to be used for coroutines that last the lifetime of the app.
This is a scope provided by the KTX dependencies. It is a lifecycle aware scope. They are defined to help stop coroutine jobs when a Lifecycle is destroyed.
This scope is also provided by the KTX dependencies. This scope is defined for each ViewModel in an app. Any coroutine launched using this scope will be canceled when the ViewModel is cleared.
You can also define and manage your own scopes, but if you have to do this I would make sure you are considering why.
💭 Quote of the Week
Not much from me this week, but I did want to leave you with something to ponder. Here is a quote from Jesse Owens, USA track and field athlete, 4-time Olympic gold medalist.
“We all have dreams. But in order to make dreams come into reality, it takes an awful lot of determination, dedication, self-discipline and effort.” – Jesse Owens
👋 Want to Contribute!?
Join the discussion on Twitter where I’ll be posting more about Kotlin and Android.
Remember to stay hydrated and have a great week!
Thanks for reading!
- Matt ✌️
What did you think of this issue? Let me know by replying to this email! I’d love to say hello :)
Don’t miss out on the other issues by Matt McKenna
Did you enjoy this issue? Yes No
Matt McKenna
Matt McKenna @himattm

Develop a thoughtful approach to software engineering.
Focused on Android, applicable to all.

You can manage your subscription here.
In order to unsubscribe, click here.
If you were forwarded this newsletter and you like it, you can subscribe here.
Created with Revue by Twitter.