As an Android developer and someone who has studied the ASOP internals, I don’t see what the big deal is. If I were going to build custom hardware that has a custom ui then it makes complete sense to start with the open source version of Android. Google has spent billions inventing that wheel and you can use it for free. It has everything you need (except realtime). The natural way to build ui apps in Android is to make an apk. Doing anything else would be weirdly unnecessary.
The bits of this controversy about "where's the LAM?" are strange to me. My impression from the beginning was that the "Large Action Model" was a server-side thing, and the hardware was going to be almost-entirely a way to talk to their services.<p>Apparently this impression was far from universal.
Why does it matter if it is an android app? Why would they redesign the wheel?<p>Criticism should be reserved for poor execution and hype over substance.
As an Android developer I don’t understand the reason behind mixing Jetpack Compose and Flutter. I’m not an expert on cross platforms, I mostly work on Compose, so if anyone wants to share.
save you a click
> We didn't find a "LAM" in the APK, but that doesn't mean it isn't happening in the backend. It also doesn't mean it is happening in the backend.
> rabbit is an android launcher
I turned down an interview with Rabbit. While I was looking into the company, I watched a product demo of theirs featuring the CEO who didn’t use the scroll wheel on the device (instead used the touch screen) and it seemed as if multiple features shown were not actually in a functional state. Kind of a weird tech stack, too, based on the job description.