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) How to fix keyboard issues introduced in the latest Jetpack Compose (1.4.0)
2) OWASP MASVS (Mobile Application Security Verification Standard) v2.0.0
3) Rebugger: A recomposition debugger
4) Google Pixel flaw allowed recovery of redacted, cropped images
5) Mastering Android App Performance: Analyzing Bottlenecks with Perfetto
1) Did you have any keyboard issues after updating to Jetpack Compose 1.4.0? Well, I did… Check out my latest article to learn about new Compose bugs and how to hack them. It is available on my official website and on Medium ✍️
🔗 How to fix keyboard issues introduced in the latest Jetpack Compose (1.4.0)
2) New OWASP MASVS (Mobile Application Security Verification Standard) release is available! This release has focused on maintaining abstraction, simplifying the standard by removing redundancies, using standard terminology to bring clarity, and narrowing the scope by relying more heavily on other industry standards. These changes aim to make MASVS more understandable and effective for users, ensuring that it remains a leading industry standard for mobile application security. The MASVS v2.0.0 was presented at the OWASP AppSec Dublin 2023, you can watch the presentation below👇
🔗 Global AppSec Dublin: "Mobile Wanderlust"! Our Journey To Version 2.0! - Sven Schleier
🔗 OWASP MASVS (Mobile Application Security Verification Standard) v2.0.0
3) Being a “Compose Dev” our enemy number one is unnecessary recompositions 🤕. Often times we use tools like recompositionHighligher, LogComposition, and layout inspector to count the recomposition, but there’s no direct way to understand “why” the recomposition has happened. Rebugger is a simple compose utility function that can track the change in the given arguments. It’ll print the reason for recomposition in your Logcat window.
🔗 Rebugger: A recomposition debugger
4) An “Acropalypse” flaw in Google Pixel's Markup tool made it possible to partially recover edited or redacted screenshots and images, including those that have been cropped or had their contents masked, for the past five years. Find out how this vulnerability worked 😬
🔗 Google Pixel flaw allowed recovery of redacted, cropped images
5) In this article Shreyas Patil presents how to investigate performance bottlenecks in the application that might cause UI slowness or janks with the help of Perfetto
🔗 Mastering Android App Performance: Analyzing Bottlenecks with Perfetto
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.