commonsware.com
Android app developer. Entrepreneur. Author. Fan of sentence fragments.
76 posts
658 followers
118 following
Regular Contributor
Active Commenter
comment in response to
post
Alas, I screwed up including the right handle for @stefanoq21.bsky.social in the post. 🙄
comment in response to
post
Ah, OK, I misunderstood. Thanks for the clarification!
comment in response to
post
They waited a while after KMP went stable before endorsing it. Since CMP for iOS just went stable, maybe Google endorses it in 2026 or 2027.
comment in response to
post
Thanks for all that you did for the Android development community. I'm glad that Google made... Room for you! 😁
comment in response to
post
Thanks!
comment in response to
post
RIP, little Droid
comment in response to
post
Nice post! However, it has a typo: "But Congress let’s" should be "But Congress lets".
comment in response to
post
I had that happen a couple of times, though not in recent days. I chalked it up to tokens being invalidated on the server due to deployments, though it is annoying.
comment in response to
post
I wish you nothing but the best in wherever life's trails lead you!
comment in response to
post
Bespoke, small batch, artisanal feeds
comment in response to
post
I use them for personal email and calendar. I have not had many problems with them, other than the occasional outage that is fairly typical of this sort of provider.
comment in response to
post
Been there! 😁
(though I'm confident that you're not doomed!)
comment in response to
post
Very cool, thanks!
comment in response to
post
Hmmm... I agree that it seems to be missing. If you look at the sources JAR for the artifact, it shows things like PlayerSurface and PlayPauseButtonState, and those are not showing up on that search engine. Perhaps the artifact was published prematurely by accident. 🤷🏻
comment in response to
post
The Commanders' future is bright. Their turnaround this season was simply stunning. This just wasn't their game.
Enjoy your trip!
comment in response to
post
In the absence of that, if an app publisher would prefer to have those limited resources work on other things, such as privacy and security, that is their prerogative. It would just be nice if they could state that intention and have it be honored, rather than just wind up with lousy UX.
comment in response to
post
In an ideal world, all app publishers would have ample resources to support every form factor and environment that Google dreams up.
In reality, that doesn't happen as often as we would like.
Google is certainly welcome to fund publishers to do this work.
comment in response to
post
> Would you block shipping the app to any foldable then?
If that is what the app publisher wants, sure.
> What about any phone... that can be connected to an external display that is at least sw600dp?
There will always be edge cases. This likely is one of them.
comment in response to
post
Since Google defines it as "screens larger than 600dp wide" in regards to the adaptive change that you mentioned, that seems like a reasonable starting point.
comment in response to
post
Will Google finally allow developers to reliably opt out of distributing to large-screen devices?
If not, then I suspect that all this change will do is switch the UX from one so-so look to a different so-so look. 🤷🏻
Large screens are not a priority for everyone, nor should they be.
comment in response to
post
I see the attached in a column to the left of your prose, just under the giant blue banner at the top of the page.
comment in response to
post
They cite you as author and link back to your post. That said, I always assumed they did this with the permission of the author and in accordance with whatever licensing the author has for their posts.
If that is not actually happening, ☹️