Android development fills me with dread, I’d much rather use the simple and elegant Resin.io approach of Docker containers.
Does anyone have any ideas on how Bridgefy SDK can be made to work on some form of a Resin.io-based setup?
Or can propose a reasonable alternative? I’m interested in local & bi-directional (in Bridgefy’s case, Bluetooth-based) connectivity between the device and iOS/Android phones, i.e. without using the Internet.
I would love to avoid having to abandon Resin.io in favour of Android Things…
Thanks @floion! Unfortunately these do not solve my problem – as I said, I’m looking for local, bi-directional connectivity between the device and iOS/Android phones. This is what Bridgefy does – https://www.bridgefy.me/learn-more.php
Hi, sorry for the quick run over your previous message.
Looking at bridgefy, it looks like currently they only support iOS and Android. So basically this would mean that resin.io would somehow need to support Android. I’m not aware of any strides in this front and I’d guess this blog post https://resin.io/blog/will-resin-io-ever-support-android/ summarizes a bit the state of things regarding Android support.
A benefit of having resin.io run on top of Android Core would be to gain the additional hardware support that Android has for a number of devices where Linux support is non-existent or substandard. A resin.io managed Android Core device would appear like all other resin.io managed devices, and, if we got a container engine and our agent running on it, would run containers pushed from resin.io.
I.e. use Android for lower-level access to the Bluetooth stack facilitated by the Bridgefy SDK, but use resin.io to create containers with the business logic. Unfortunately, since this isn’t available right now, I’ll search for another solution!
