forked from Blendman974/faceclaw
Add app tool registration for voice assistant; voice assistant can read and send to terminals
This commit is contained in:
1 parent
0aeb24ed00
commit
fe205c0164
9 files changed
+533
-16
No files matched your search
@@ -0,0 +1,87 @@
|
||||
# Even-Analogous Apps
|
||||
|
||||
Ideally we'd like full feature parity with the stock Even app (or at least,
|
||||
close enough that not-using the stock app doesn't feel like a sacrifice).
|
||||
A rough list of things the stock app has that we currently don't:
|
||||
|
||||
## Quicklist
|
||||
|
||||
Quicklist is Even's version of a todo app, in the form of a dashboard card
|
||||
that you add to and remove from with assistant voice commands. It's pretty
|
||||
simple to build once a general voice assistant is in place, but I don't
|
||||
actually like their design: a todo list really wants to be synchronized
|
||||
with something external like Roam or Notion, so I think it'd be better to
|
||||
build one of those integrations instead.
|
||||
|
||||
## Stocks, News
|
||||
|
||||
Even has a dashboard card which is a stock ticker. I think this is probably
|
||||
misguided; while there do exist people who would want and benefit from a stock
|
||||
tracker on their glasses, I do'm not sure there exist people who would want and
|
||||
benefit from a stock tracker that isn't a professional-tier tool connected
|
||||
to carefully chosen low-latency data sources, and neither I (nor Even) can
|
||||
build that tool.
|
||||
|
||||
The News dashboard card is more broadly useful, but has a similar issue: a
|
||||
generic news ticker isn't really useful without a much higher degree of
|
||||
customization. Probably the right thing to build instead is more like an RSS
|
||||
reader.
|
||||
|
||||
## Ring Connection Management
|
||||
|
||||
The stock Even app is responsible for pairing the glasses with the ring (ie,
|
||||
sending the glasses a configuration messages telling it to connect to the
|
||||
ring's MAC address). If you pair them in the stock app and then switch to a
|
||||
custom app, they remain paired indefinitely (this configuration is stored in
|
||||
flash), and our custom app can make use of the fact that they're paired.
|
||||
|
||||
We don't yet have support for connecting or disconnecting the glasses and ring
|
||||
to/from each other. For latency reasons, it would be nice if we could unpair
|
||||
the glasses from the ring and connect the phone to it directly; we don't yet
|
||||
support that either.
|
||||
|
||||
## Ring Health Metrics
|
||||
|
||||
The R1 ring contains an oximeter-style LED sensor and an accelerometer, which
|
||||
can be used for a step count, heart rate measurement, etc. I'm not sure
|
||||
whether the sensor interpretation is done within the firmware (in which case
|
||||
it would make sense to display them in the UI) or in the Even phone app (in
|
||||
which case we'd be reimplementing all the interpretation algorithms, which
|
||||
isn't worth it.
|
||||
|
||||
## Navigate
|
||||
|
||||
Even has a Navigate app, which is basically Google Maps for the specific use
|
||||
case of "name a destination, get turn by turn directions to there". I believe
|
||||
this is using Mapbox, which takes care of most of the heavy lifting (if you
|
||||
have an API key). I don't think Even's version is very good (they ran into
|
||||
trouble with image-upload performance preventing a good map display size), so
|
||||
it's likely not too hard to do better. One caveat is the location permission;
|
||||
Android normally only wants to prompt for location permission "while using the
|
||||
app", but Android's idea of in use (phone screen unlocked and window focused)
|
||||
doesn't match our idea of in use (G2 glasses on, phone could be locked). This
|
||||
app also gets a lot better if we figure out how to use the device's
|
||||
magnetometer (if it indeed has a working magnetometer).
|
||||
|
||||
## Distance/Viewport Configuration
|
||||
|
||||
During glasses onboarding, the stock firmware has you select a vertical offset
|
||||
for the screen image. This accounts for glasses resting at different positions
|
||||
on your face (the optics don't let you see the whole screen area), but cuts
|
||||
the usable screen height from 480px to 288px. There is also a "distance"
|
||||
config option in the stock Android app, which adjusts the horizontal position
|
||||
of the image on the two lenses separately to create the impression of the
|
||||
image being closer or farther; this cuts the usable screen width from 640px to
|
||||
576px. Unlike the vertical size reduction, this 64px reduction is not
|
||||
optically necessary.
|
||||
|
||||
## Even AI
|
||||
## Translate and Conversate
|
||||
|
||||
## Other Configuration
|
||||
|
||||
Brightness, head-up trigger
|
||||
|
||||
|
||||
# Other Apps
|
||||
|
||||
Reference in new issue
Block a user