Saúl Molinero retweeted
Here is my new article on one of my favourite features released in @intellijidea 2024.3.
The Redesigned Structure tool window helps in understanding and exploring the codebase.
A quick peak at a #SpringBoot application using Structure tool window.
Introducing the Logical view in the Structure tool window! 🎉
Effortlessly navigate your codebase, understand dependencies, and perform actions—all in one place.📦
All the details are here 👇
jb.gg/lld95m
Saúl Molinero retweeted
But then comes a revolutionary new feature to Kotlin - compiler plugins, and one thing it allows is defining types based on file analysis. So when you reference a CSV in your project, some plugin can analyze it and generate type appropriately.
Saúl Molinero retweeted
Building UIs with Jetpack Compose:
How it started How it’s going:
#TheAndroidShow
Saúl Molinero retweeted
Here are a few animations and interactions in Pinnit that we made 😁
#JetpackCompose #IndieDev
Introducing Pinnit - again! Yes, after 4 years, @edpratti and I are revisiting one of our favorite projects, and this time, with @materialdesign 3 and new features! 🧵
@RevenueCat #shipaton #indieapps #android #compose
Saúl Molinero retweeted
An animated SegmentedControl component implemented in Compose using:
- Modifier.animateBounds(), new in 1.8.0-alpha01!
- LookaheadScope
- Custom Layout
Code: gist.github.com/alexjlockwoo…
Saúl Molinero retweeted
La vida de Renato Tapia se complica aún más: anuncia su separación
⚽ El jugador del Celta comunica el final de su relación con Andrea Cordero mientras siguen sin despejarse las dudas sobre su futuro futbolístico
🔗 farodevigo.es/celta-de-vigo/…
farodevigo.es/celta-de-vigo/…
Saúl Molinero retweeted
The feature all Android developers were waiting for is finally ready! Explicit Backing Fields are available in Kotlin 2.0. You can have different types for private and public usage.
To enable it, you need Kotlin 2.0 and a special flag in your Gradle configuration.
Saúl Molinero retweeted
Yup, LookaheadLayout is a new concept that we've been building. I can barely contain my excitement about the possibilities it opens up, shared element, auto-resizing, and more! 🤩🥰 Should be ready to release soon.
Spoiler: LookaheadLayout + movableContentOf = 🤯
Sneak peek: 👇
Introduce LookaheadLayout for Jetpack Compose.
This allows us to look ahead and calculate a new layout while allowing the actual measurement & placement of every frame to be different than the pre-calculation.
Morph animation, SharedElementTransition.
android-review.googlesource.…
Saúl Molinero retweeted
Property observers like willSet and didSet aren't triggered during initialization in Swift. I wrote a post about some workarounds we can use if we do need to execute logic from property observers before we return from the initializer: nilcoalescing.com/blog/Trigg…
Saúl Molinero retweeted
Staff Android Engineer, @manuelvicnt , aims to summarise the #AndroidDeveloper guidance on the UI Layer in this article series.
Find out all the entities involved, understand the role each part plays, and discover best practices!
Check out part 1 ✨
medium.com/bumble-tech/crash…
Implementing an animated column section header using Jetpack Compose - DEV Community dev.to/tkuenneth/implementin…
3
498
Saúl Molinero retweeted
✨ shimmer✨
#AndroidSpotlight
If you need to Shimmer & Shadow loading animation with Jetpack Compose, feel free to check the Medium article with GitHub Repo: proandroiddev.com/shimmer-sh…
Two mutables don’t make a right - Zach Klippenstein - Why you shouldn't use mutable objects in your State holders dev.to/zachklipp/two-mutable…
6
840
How the Snapshot system works in compose. By Zach Klippenstein. A must.
dev.to/zachklipp/introductio…
5
532
Saúl Molinero retweeted
Just published part 1 of **BasicTextField2: A TextField of Dreams**, on the new TextField API 🥰🚧🏗️
medium.com/@astamato/basicte…
Enjoyyyyyy 📕📗📘
Second part coming soon :)
#androiddev #jetpackCompose
Saúl Molinero retweeted
Compose Tips:
In Jetpack Compose, the Compose compiler defaults to treating an interface as unstable because Compose lacks information on its potential implementations.
For instance, when you create a Composable function containing a `List`, it's regarded as unstable since the `List` interface is inherently unstable. This stems from the fact that `List` can be implemented in mutable ways, such as `MutableList` or `ArrayList`. To address this, consider using `kotlinx.collections.immutable` packages.
When you create an interface that needs to be applied with the smart recomposition, you should explicitly mark it with the `Stable` annotation. This annotation signals its stability to the Compose compiler.
If you want to learn more about the Compose stabilities and optimize your App performance, check out the article `6 Jetpack Compose Guidelines to Optimize Your App Performance`.
🔗: proandroiddev.com/6-jetpack-…
Saúl Molinero retweeted
Pull to Refresh is finally coming in the Material 3 library!
I've heard that some developers out there are not using the M3 library because this was missing.
Are you using Compose M3 already? If not, will you use it once the it is released?
“The Diffing Dilemma! All about diffing with LazyLists!” by Garima Jain
medium.com/google-developer-…
Saúl Molinero retweeted
Yay #AndroidDev, here it is, my very first tutorial 🙌!
I hope some of you find it useful. Feel free to reach out for feedback
composable-fun.ghost.io/list…
Saúl Molinero retweeted
Progressive Rendering in Compose Preview released with the goal of making previews more performant. Decreasing render quality saves on memory used and improves the usability of Preview.
Give it a try → goo.gle/46NNbz1





























