2 min read

Issue #26

New Podcast episode, kotlin-inject, VisualTransformation, Kotlin’s Context Receivers, and do NOT use this cryptography library! 😳

Hey! 😄

Time for another issue of the Android Dev Newsletter 🗞️
Here’s what I have for you today 👇

If these links don't work in your email client, try reading this issue on my website.

1) New “AndroidTalks” Podcast Episode! “AT 05 - [OWASP Mobile Top 10] M1: Improper Platform Usage”

2) From Dagger & Hilt into the multiplatform world with kotlin-inject

3) Jetpack Compose: VisualTransformation Made Easier

4) Exploring Kotlin’s Context Receivers

5) Do NOT use this cryptography-kotlin library

1) My new Podcast series in which I explain all points from OWASP Mobile Top 10. If you’re a Polish speaker you can listen to it at the link below. If not then soon I’ll be posting an article in English about it! 😊

🔗  AT 05 - [OWASP Mobile Top 10] M1: Improper Platform Usage - Nieprawidłowe używanie platformy

2) In this article a dev working at Klima explains how they are taking advantage of Kotlin Multiplatform to build their new app “Planet Wild”, using new dependency injection library from Eva Tatarka, kotlin-inject. It also helps you understand how to migrate to kotlin-inject if you’re coming from Dagger or Hilt.

🔗  From Dagger & Hilt into the multiplatform world with kotlin-inject

3) This article shows how to easily use the VisualTransformation API in a TextField using phone number formatting as an example.

🔗  Jetpack Compose: VisualTransformation Made Easier

4) In February 2022, Kotlin 1.6.20 was released, introducing context receivers for the first time. This design proposal solved the popular use case of adding context to Kotlin functions. Context could already be added through extension functions, but the proposal allowed multiple receivers. This article explains how to use context receivers, starting with basic examples and then showing more advanced ones.

🔗  Exploring Kotlin’s Context Receivers

5) This library was made to help you build Multiplatform apps and have a type-safe cryptography library in Kotlin. BUT I do not recommend using it. All cryptography functions should be used directly from the Platform - iOS or Android. That’s the only way to make sure you’re using them right and the implementation is correct. Using any kind of library from GitHub and unknown sources may lead to huge security holes and issues. So, if you want to have cryptography in a KMM app then it should be implemented separately on iOS and Android parts.

🔗  Do NOT use this cryptography-kotlin library

That’s all for today. Don’t forget to recommend this Newsletter to a friend or someone who might be interested 😊

Thanks for reading and see you at the next one!

All the best,

patrykkosieradzki.com | androiddevnews.com | androidtalks.com

Would you like to ask me something?
Just answer this email and I will be happy to get back to you!

If you’d like to read previous issues, please visit the archive on my website.