TW for tiny interfaces (and a free watch browser)

#1

I recently bought a (used) applewatch…and finally found a free webbrowser.

Has anyone made a TW for so tiny interfaces.

  • I would love to use TW as a micro note-taking tool, where I say a phrase which is stored to my NoteTW to be transferred to the correct wiki subsequently.
  • A tool to learn vocabulary and other things would also be nice as well as well as
  • a tool to make an audio playlist from websources
#2

Totally possible, just create a new layout, which only has a big voice input button, and can scroll to view transcribed text.

Simillar to Design a Layout for Mobile

#3

https://makiaea.org/00045/20230414makiaea.html#apple%20watch

i have a layout working (single file), but don’t normally use it as loading is so slow, and possibly saving does not work (sorry i don’t remember if i tested saving using a served file)

you’d have to get a back end for saving working (pwa does not work as browser too limited)

maybe a node version would work better for loading/saving?

i use the paid browser listed in that tiddler, ‎Browser for Watch on the App Store as i find its bookmark feature useful

hth!

1 Like
#4

This is not a direct TW interface, but I highly recommend “Just Press Record” — an app that can actually appear as a simple red dot complication on your watchface. Touch it just once, and it’s already in record mode (touch it again to stop recording). On your phone or even macOS you can access both the audio and an automatic transcription for all notes entered this way.

This means I can generate reminders or notes with zero interface friction, even while stopped at an intersection or walking the dog.

I still need a work flow to comb through this “inbox” of notes and decide what to do with them. But usually when I’m out in the world and wanting to get something down via my watch, the process is very off-the-cuff anyway, and further editorial decision-making will be needed before I’d want to commit to whether and how this idea or information belongs in a tiddler.

#5

You can use tidme plugin to remind you organize them.

1 Like
#6

I have considered something like this before, but this post inspired me to run some tests.

I am running WearOS on the PixelWatch connected to Android on Samsung.

Running Tailscale on my watch, and using bluetooth as my connection (rather than its onboard wifi or LTE), the PixelWatch can access all of the ports that I have exposed on my VPN, including my wikis.

My main wiki, where I would want to have notes stored, takes quite a while to load, but an empty wiki takes only a moment.

I imagine that a viewtemplate which transcludes the content of a particular tiddler without a frame on any screen 450px x 450px or less would not increase loading times significantly.

The transcluded tiddler would contain a single (red) button that would record a voice input – the voice input could be passed to an LLM for voice-to-text and then added to a tiddler with a preformatted title. Those notes could then be shifted from the watch wiki to the main wiki.

Multi-Wiki-Server would make this process even more streamlined.

Additionally, this text could potentially not just store notes for the future, but it could be stored and the tasks could be performed later – for example, if you were to say “Make a task to Update the Watch App” that information would be stored as text – and if you passed those notes through an LLM when you return to the main wiki, it would be able to differentiate between tasks you’d like it to perform vs notes you’d like it to store.

If you strung together multiple agents that can communicate (I believe openAI is calling this a ‘swarm’) you could have those tasks performed on the fly – have the initial API call convert the voice to text and send that to your “main-wiki-agent” and perform a task, or include a google API to add the task to your google calendar and so on.

Speaking of MWS, it occurred to me that the SQLite database might load significantly faster than the .tid system – a quick test confirms that the MWS server I’m running, which contains backups of nearly all the tiddlers and plugins within my main wiki, does load significantly faster… about half the time (90 seconds).

I did have to disable the datepicker plugin for this to work, and I have my sidebar open by default and no button rendered which could close it – but otherwise it looks fairly functional and I think a relatively short amount of work could create a viewtemplate that would create a reasonably user-friendly interface.

1 Like