For gesture navigation, if not testing with it, there might be interactive components that interfere with the gestures - for example, a slider or range slider, or a component with swipe-to-dismiss actions.
#AndroidDev #Android #AndroidAccessibility
Compose (or Android) tip: Test your app with both button and gesture navigation to avoid breaking the user experience.
When not testing with button navigation, it's easy to forget to leave enough padding for the buttons, which, in turn, can make some elements unusable at the bottom of the screen.
Maybe I'm missing something, but does anybody actually still use the standard text UI feature of "click & drag selected text to cut & paste it somewhere else"?
I've done it thousands of times and literally every single one has been accidental.
You shared that androidx libraries are constantly in alphas and we listened. In the past two years while adding a ton of new libraries we actually increased the percentage of libraries that are complete or actively developed.
The combo of these two groups went from 64% to 76%.
#androidx #androiddev
It's so satisfying to kick the tires on Metro and see that it is, in fact, what I wanted and dreamed of: Anvil with the sucky parts removed
There are a lot of benefits of building for local-first offline-only. Offline apps are severely underrated. You don't need a server for most things (terms might vary; we're building different things, too).
KSP is now independent of Kotlin versioning!
github.com/google/ksp/r...
Geodesics on spheres are always arcs of great circles. Geodesics on a cylinder can be segments of spirals, though.
Geodesics are (in one definition, at least) the shortest distance paths between two points on a surface.
I personally keep all my app modules together in an app folder (so technically they are submodules of :app), and also stick a kmp :app:shared module in there as the entry point for all of the platforms. Then everything else is just pure kmp modules (no "shared" prefix needed)
😢
a checkbox on a website that says "keep me logged in"
There are three kinds of lies: lies, damned lies, and
Y'all gotta stop buying smart TVs, so they stop making them. There is literally nothing appealing about them.
My TV doesn't show me ads when I'm just turning it on. It can't be ruined by a software update. It turns on and off when I want it to. It immediately responds to all inputs.
I wonder if "Accessibility" would be less of an afterthought, and more people would be interested in it, if we renamed it "Best Practices"
Magic the Gathering card with text "Exquisite Blood. Whenever an opponent loses life, you gain that much life"
Magic the Gathering card with text "Sanguine Bond. Whenever you gain life, target opponent loses that much life."
The very first infinite combo I discovered on my own while building decks in Magic the Gathering
Which is all to say that @johnoreilly.dev is right here, but it applies 100x more when someone raises an issue about clarity and confusion.
If someone says they don't understand a process, then the documentation of that process needs to be created or updated, etc.
After thinking about it for another minute or two, I realized he couldn't be wrong. A piece of code is confusing if someone reads it and is confused, which was the case here. Objectively, he had to be right to at least some degree.
Early in my career, I wrote a piece of code that I thought was the most beautiful idiomatic piece of Kotlin code one could write. My manager commented in the code review that it was confusing.
My gut reaction was that he was wrong and probably too entrenched into Java idioms still...
It always seemed insane to me that I was in the minority in grad school for preferring whiteboards. When I asked people why they preferred chalk, they would often tell me that whiteboards are messy? Like... messier than chalk?
Neat. What defines a "valid" location? Not within a distance of r from any other point?
Model holding a concept version of the Project Ara phone. It features a number of modules in colored plastic or metal, a camera, and a simple display screen for the back.
I'm sad that Project Ara never came to be. The idea of modularity for a phone was a cool idea. Definitely get why it never went anywhere, but dang it would have been cool.
The idea was you buy a phone chassis and then modules that give features, storage, extra battery, etc.
Birth cerificate: born Jan 01, 1970 at midnight on null island to parents "" and "".
Arguments and return values of your service methods should be models and not services.
Constructor injected objects should be services (most of the time).
The "glue" in this article is going to include the things that do actually take services as arguments/return values (like your DI framework).
Services/injectables should have their own unit tests.
Models/newables are tested implicitly by the unit tests of the services they're used in, and thus shouldn't need their own unit tests.
Knowing this difference is important if you are trying to write clean testable code w/ dependency injection:
Services/injectables should always be injected as a dependency where they are used and you should use test doubles where they are injected.
Models/newables should never use test doubles
To add to the nomenclature of this short article:
I have also seen "value classes" defined as "models", "entities", and "newables"
"Service objects" would equivalently be "services" or "injectables"
Lol, it's me at a punk show.
That's a really interesting bug. I don't think I fully understand why the objects aren't instantiated when the companion object is instantiated, though. Seems like a language bug rather than a dev-side bug to me.
The biggest trick the devil ever pulled is to call LLMs “artificial intelligence.”
Email addresses are very simple, and you will score highly in this quiz.
e-mail.wtf
