You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! Yes! I think that working with an android java companion app would be the best method because then the Pebble Assistant can tap into everything the device is offering. There appears to be a significant difference between "cloud" assistant and "native" assistant. Unfortunately I have no Android development experience and that is why I went the JS route for the proof of concept.
For your second point, making it available in Pebblekit... I tried that as well. The compiler for pebblekit is a bit rudimentary and doesn't like lots of tokens that come in modern packages (like async / await statements and other typescriptish stuff). It may be that some aspects of the endoplasmic RPC build could be re-written to make it pebblekit compatible?
I have been trying to find out more about the pebblekit environment and what does and what doesn't work and how to test if a different built would work but... there's not a ton of information out there and it's a bit hard to get the ear of people who would know.
Any chance we could make this work with an android java companion app instead of firebase?
Or perhaps doing something like the link below to compile down the service to run on the phone app?
https://therin.me/2013/12/21/using-npm-packages-in-pebblekit-js-apps/
The text was updated successfully, but these errors were encountered: