Brief Description: Some of you tested this here back in July when it was a watch face. It's an app now, so it works with whatever face you already use, and it's finally live on Play. You put in your pay and your shift once and it shows how much of today's pay is left, counting down while you work. Tap the number if you'd rather watch what you've made so far go up.
The tile, weekly overtime, and the app working out your full day's pay on its own all came from people here during testing, so thank you for that.
Free gets you the live number, the watch app, the tile and complication, your unpaid break taken out, and buttons to fix your time or add tips. You can even set it up from the watch without touching your phone. The unlock is extra stuff like clocking in and out yourself, weekly overtime and a payday countdown.
Cost: Free. Optional one-time unlock, $3.49 in the US and less in a lot of other countries. No ads, no account needed.
Im vergrößerten Schlafdiagramm sehe ich meine 4 Schlafphasen aber nicht Spo2 und die Herzfrequenz. Auch wenn ich eine Schlafphase abwähle kann ich Spo2 oder Herzfrequenz nicht auswählen. In den Trainings und Gesundheitseinstellungen ist Spo2 Verfolgung aktiviert.
The interface I created is finally on sale and currently at half price. If you're interested, please take a look. If anyone experiences any problems after purchasing, please contact me. I will release an update regarding the issue the same day, but keep in mind that Google takes a week to approve it.
The GIF above is the watch app driving a desktop cursor. Here is the full demo video (27 seconds).
wear-pointer has three pointing modes you can switch live:
LASER: aim with your wrist and the cursor goes where the watch points.
AIR: relative gyro air mouse with acceleration.
TOUCH: use the watch face as a touchpad.
Tap to click, hold to drag, right click, pause, recenter, and the bezel scrolls. DPI goes from 400 to 3200.
There are two ways to connect. BT HID makes the watch a standard Bluetooth mouse, so you pair it in your computer's Bluetooth settings and nothing gets installed on the computer. BLE APP uses a small tray app for macOS, Windows and Linux (Hyprland) for a higher rate link. The test logs in the repo cover the BLE APP path. BT HID is newer, so reports on how pairing goes with your OS are especially useful.
I've only tested on a Galaxy Watch7 (Wear OS 6). It needs Wear OS 4 or newer with a gyroscope. If you try it on another watch I'd like to hear how it goes.
Code is MIT on GitHub. GitLab is the canonical repo and CI, and the free signed APK is on the GitLab release. A paid Google Play listing is planned as an optional way to support development. It is not public yet, and the APK stays free.
Hi everyone one, im stuck here with my basically brand new pixel watch 3. The Lock screen won't turn off no matter how many times factory reset , i tried to update by official OTG update but not luck same thing. Now the watch on very old version 2025/6/ security update that's last update on it android 15. I have been doing this by pixel flasher. And again no luck. Can any one help me with this.
tl;dr: Samsung health sucks for sports so I made an easy to use one button rest timer and HIIT routine app for Wear OS and I'm looking for testers atm (see bottom of this post).
Coming from Garmin one thing I've missed is their workout UX and UI, every sport had a specific well thought out functionality. Especially the one button press set/rest for weightlifting and interval routines with specific targets like cadence or heart rate zone. SHealth is very bare bones and I couldn't find any 3rd party equivalent in Play store, so here it is! Not only that, but Setloop supports Bluetooth sensors as well. I've tested this only with my Garmin Cadence Sensor 2, but any sensor that uses the standard Bluetooth profiles should work (ANT+ only not supported)
Setloop has a mobile app as well for history, workout routine editor and customizing the workout screen data fields.
Here's the Play Store page's description:
ONE BUTTON FOR THE WHOLE WORKOUT • Use the side back button on Galaxy Watch, or the large on-screen button on other watches. • In a free session, the rest timer counts up until you start the next set. • In a routine, each rest counts down to your planned time, and the watch vibrates when the rest is over. • Tag a set with the exercise, reps and weight, or skip it and keep training.
HIIT INTERVALS • Set work time, rest time and rounds on the watch, or make HIIT routines in the phone app. • Strong vibrations mark each interval, also when the screen is off. • Add a cadence, speed or heart rate zone target. The bezel ring turns into a gauge that shows if you are inside the target.
HEART RATE AND SENSORS • Live heart rate, heart rate zones and calories from your watch. • Connect Bluetooth sensors that use the standard Bluetooth profiles: – Heart rate chest straps and arm bands, for example from Polar, Garmin and Wahoo – Cycling speed and cadence sensors – Cycling power meters – Smart trainers and gym machines with Bluetooth FTMS – Running foot pods • A chest strap can give a steadier heart rate during heavy lifts. • Set your max heart rate once, and the zones follow it on the watch and the phone.
ROUTINES AND HISTORY • Make strength routines in the phone app: exercises, sets, reps, weight and rest time. • Routines sync to the watch. Start one with a tap. • Every workout is saved on the watch and in the phone history, with set times, rest times, heart rate and calories.
PRIVATE BY DESIGN • No account or analytics. • Your workouts stay on your watch and phone.
I'm currently in the closed testing phase. If you're interested:
Note that there might be some delay before that Play URL functions. I had problems with the android specific link not listing my Galaxy Watch in available devices for reasons unknown. In that case use the desktop link to install it on your devices
If you find the app good please stay opted-in the test and keep it installed 14 days minimum. This is Google policy to get the app published on the store
Hey r/WearOS. I got tired of my watch answering to Google, so I wrote a native Wear OS client for Hermes, the open agent framework from Nous Research — several of them, each with its own job. It's a plain Kotlin and Compose app, one icon on the watch grid, and every setting you touch day to day lives on the watch. There is a companion plugin that adds a pairing page to Hermes Desktop, but that's the setup ceremony, not the product. MIT, no ads, no trackers, and after setup the only machine that ever sees one of your prompts is your own box. I wear a Galaxy Watch Ultra; everything here was built against that hardware and the Wear OS 5 emulator.
It is a watch app, not a phone-app stub. Compose for Wear OS, one icon on the watch grid, no phone companion app, and no vendor server sitting in the path. The watch is its own network node — an embedded WireGuard (tsnet) client — and it dials my gateway over a private tailnet lane.
What it does on the wrist
One orb is the interface. Tap it, talk, and a pause sends it — voice-activity detection runs on the watch. Tap again mid-sentence to throw the half-line away; tap after a pause to send right now. While an answer streams the orb burns red and one press cancels the server-side run, not just the UI; while it speaks, the same press just mutes.
Hold the orb and a dial opens: eight wedges, every 45°, each with an icon and a label — keyboard, mute, settings, commands, model, sessions, agents, approvals. Keep the finger down, slide to the angle you want, let go and that lane fires. Sessions sit at 7:30, agents at 9:00. Every wedge is remappable, and you can spin the ring a slot per detent to raise the low one.
Three screens, and back never quits. Chat, sessions, agents. On a main screen the back button walks the ring — Chat → Sessions → Agents → Chat — so the app never finishes by accident. Home leaves it; double-press home is the daily-driver way back in.
Sessions are shared state, not per-device. The sessions screen lists every session your agent has, newest first, with a chip row to filter: all, per-agent, 💻 computer, archived. Search is voice-or-type and hits the gateway's full-text index across every agent, with the matching line quoted back. Long-press a row to fork it, archive it, or delete it behind a real double-tap confirm; archived is not gone (♻️ restores it). A session you started at the desk adopts onto the wrist with its whole history and keeps answering for the desktop too.
Approvals ride the chat. A gated tool call pauses the run and the card comes with it. Scroll it off-glass and the answer moves to the orb's flanks — ✅ left, ❌ right. Or answer it from the notification shade without opening the app. The approval level is per chat: Manual, Smart (auto-approve while you're away, ask when the chat is on your glass), Inherit, Off.
It keeps working when the app is not in your hand. A session running at your desk has no stream pointed at the watch, so the app sweeps the gateway's inbox: every 20 seconds in the foreground, and once the app is backgrounded a WorkManager chain takes the shift, re-arming itself about 60 seconds at a time (periodic work can't be scheduled under 15 minutes, so it's a chain of one-time jobs). That exists because Samsung's cached-process freeze killed the in-app loop within a minute of pressing home on this hardware — so the chain re-schedules before it sweeps, and one bad sweep can't end the lifeline. Chain and in-app loop share one cursor, so the handover can't buzz you twice. Honest limit: while Doze seals the network, the sweep waits for a maintenance window and latency is minutes, not seconds.
A notification is a door, not a toast. Parked approvals and finished answers land as ordinary Wear notifications; the approval card carries Approve / Deny in the shade, and Open or a tap drops you into the exact session that produced it, switching agents first if it has to, history intact. Dedup is by session-and-tool, and an answered park goes stale and is forgotten, so the next park buzzes again; "answer ready" fires only when a session's message count grew and the newest row is the assistant's — someone else typing in a shared session does not ring your wrist. Cron runs ring too: ⏰ job-name ✓ finished / ✗ failed, per agent all/failures/off.
It never notifies you about what you are already looking at. If that chat is the live thing on your chat screen, the answer renders inline and speaks, with no notification; anywhere else it goes to notifications and stays silent. One decision function picks the channel for both halves, deliberately — voice leaking out of a pocket and a buzz for something already on your glass are the same bug wearing different clothes.
Content that survives 1.4 inches: streaming markdown, real tables up to four columns, images full-res, animated GIFs that actually animate, a fullscreen video and audio player where the rotating bezel steers the volume (5% detents, haptic tick each), pinch-to-scale text across the whole range (×0.75 to ×1.6, double-tap resets), edge-drag scrolling so you roll the rim of the glass instead of losing your thumb, and a ⌘ lane listing your gateway's commands plus your agent's own skills.
Per-chat model picker, by the way — it lists whatever your gateway exposes and the header says the scope: this chat only.
Body tools, opt-in with both toggles off by default: heart rate and steps, fed to the agent. Sleep and blood-oxygen toggles are wired but Samsung exposes neither to Wear yet, so I'd rather say that than ship a dead card.
Voice, and what it costs
Input, your pick, and the picker labels each one honestly: Parakeet Unified 0.6b on my box (the default; streams partials while I talk, so the transcript is nearly finished when my sentence is — the mic clip rides as Opus 24k mono, about 10× lighter than a wave), local Vosk on the watch (offline, airplane-mode dictation; the model is one tap in Settings ▸ Voice in, 41 MB download / 69 MB unpacked, Range-resumable, and it only flips to installed after the acoustic marker verifies), the vendor's recognizer labelled plainly OFF-DEVICE, or the keyboard's own mic. Output defaults to NeuTTS Air on the gateway, synthesised by paragraph so you don't get machine-gun cadence between chunks, and the glass follows the spoken sentence teleprompter-style — the word timing comes from the same engine that just heard me. No gateway? It falls back to the watch's on-device TTS instead of going silent, and the About page names which tier is live.
Voice cloning takes 3 to 12 seconds. Enroll a person once and the gateway clones the take into the engine on my own CPU — no vendor voice API, no per-character bill. The watch has its own enroll screen: name it, record the line once, hear it back, retry or accept, recorded on the watch mic and capped at 12 s so a wander can't bloat the sample; under 3 s is rejected on the watch and the length is re-proven gateway-side. The Desktop pane does the same job from a microphone on the box. Each agent gets its own voice, and the assignment is a single preference in a canonical store with a monotonic revision and a higher-revision-wins two-way merge — so a voice picked at the desktop appears on the watch, one enrolled on the watch appears at the desktop, and a watch that was offline reconciles when it returns instead of clobbering. Changing voices doesn't reload anything either: the card is a zero-shot reference handed over per request. Per-agent mute and reply volume live on the watch too (Voice-out page, and the mute lane on the dial — dwell two seconds and the ring becomes a volume slider for this agent). Endpointing is good enough that it holds up in a loud room when Parakeet is on the other end.
Weight, cache, battery
106 MB today, and the APK's own entries say what that is: ~44 MB is the embedded WireGuard node (the price of no LAN path and no relay), ~18 MB the Vosk binary, ~41 MB unshrunk dex — debug builds skip R8, and the hardening pass is on the roadmap; the Release APK in GitHub Releases is CI-signed and zipaligned. The app writes no disk cache at all: 25 KB in cache/ after a full day of streaming, images and voice. History lives in the gateway's session store and the watch keeps nothing but the session id it's riding, so six months out the footprint is the size it shipped at.
Battery honestly: the tunnel is held by one ongoing specialUse foreground-service notification — deliberately notdataSync, whose 6 h/day cap would tear the connection down every night, straight out of the manifest comment. That ongoing notification is the cost, and I'm not going to quote you a percentage I haven't measured on your watch. Install it, wear it a week, tell me what you see.
Getting it
Repo:https://github.com/borealBytes/hermes-wearos — that one repo holds the watch app, the plugin, the screenshots and the CI. Today's build is v0.10.12 under Releases: the APK with SHA256SUMS.txt beside it, sideload takes about a minute with developer mode on the watch. No Play Store yet: I've started the Google Play developer account, so until that clears the APK is the only path, and pairing goes through the plugin either way.
The plugin side:https://hermes-agent.nousresearch.com/marketplace/wearos — one plugin (wearos) adds a Wear Kit page to Hermes Desktop where the pairing window opens, you choose which agents the watch may reach, and readiness lights tell you what's not green yet — every red names the exact command that fixes it. It also carries the pinned, checksummed Parakeet installer and the per-agent voice dropdown. Everything you actually use while wearing it is on the watch.
Pairing is worth a sentence because it's the part people get wrong: the 6-digit code is minted by the gateway, never by the watch, and it never passes through a model. The pairing window is closed by default, opens for five minutes, one pairing per window. You approve on your computer. The watch then collects a single-use Tailscale enrollment key (24 h, tag:hermes-watch, zeroed from the ledger the instant it's collected) and from then on it carries a device token; the gateway resolves who's calling with tailscale whois on the peer IP, binds your node to your device on first sight, and refuses a different node wearing the same token. Revoke is full removal: node deleted, token invalidated, outbox cleared, API key rotated.
Disclosure: I built this for the Hermes Agent hackathon that Nous Research ran, which closed last week, and it is listed in the official catalog as wearos under the name Hermes Wear Kit (link above). Official judging is still running, so I am not making any claim about where it landed.
Fine print, since this is a privacy subreddit: no telemetry, no analytics, no crash uploader. Outside the tunnel it touches api.tailscale.com (enrollment keys, device list, node delete on revoke), and github.com / pypi.org / huggingface.co only when you press Install on a voice engine — Tailscale's control plane brokers the key and its DERP relays are in the path. I say that plainly rather than saying "no cloud" and letting you find the exception later.
Still in the works: the watch-face complication and the Ask Hermes tile.
Judging notwithstanding, I would take the beating: install it, break it, and tell me which feature you would expect to see and don't. Screens are off the Ultra and and Hermes Desktop; the dial shot is the honest layout, not a mockup.
⌚🔥 [TESTERS NEEDED - WEAR OS] Test for Test (14 Days) – JAPJ Retro Radial Premium 🔥⌚
Hi everyone! I'm looking for 12 testers with a Wear OS smartwatch (Galaxy Watch 4/5/6/7/Ultra, Pixel Watch, etc.) to help me complete the 14-day closed testing requirement for my new tactical retro digital watch face: JAPJ Retro Radial Premium.
Brief Description of app's features: A standalone Wear OS camera viewer with a feature-packed Android companion app and diagnostics toolkit for RTSP, ONVIF, and IP streams with zero cloud dependency:
Wear OS Features:
Standalone Streaming: Plays live camera feeds directly on round watch displays (192dp & 227dp layouts) without needing the phone active.
Tiles & Complications: Dedicated Wear OS Tile for instant preview and Watch Face Complications for one-tap camera access.
Phone Relay Engine: Can use local phone-assisted relay over the Wear OS Data Layer when the watch's standalone Wi-Fi signal is weak.
Phone Companion Tools & Embedded Server:
Built-in Local Streaming Server: The phone app can run its own local HTTP/MJPEG camera server, turning your phone into an IP camera feed on your LAN for streaming to Android TV or your watch.
ONVIF WS-Discovery: Automatically scans and detects ONVIF cameras on your local network (Tapo, Reolink, Dahua, Hikvision, Axis, Amcrest, etc.).
Port Sweep & RTSP URL Finder: Built-in network tool to sweep IP ranges and brute-force common RTSP paths to discover hidden/silent cameras.
MQTT 3.1.1 Monitor: Test broker connections and monitor live topic payloads with optional TLS.
go2rtc API Discovery: Inspects producers, consumers, and codec payloads before importing streams into the app.
ONVIF Profile T Tools: Control PTZ, recall presets, adjust imaging parameters, and trigger digital inputs/relays.
Integrations & Ecosystem:
Home Assistant: Direct import of camera entities using an encrypted long-lived access token.
Frigate NVR: Event timeline review with authenticated snapshot previews.
Multi-Device Support: Phone/tablet MultiView grid (4+ simultaneous streams) and an Android TV Leanback app with D-pad navigation and QR-code pairing.
Automatic Sync: Configure cameras and tools once on the phone; records sync to the watch via Wear OS Data Layer.
Privacy & Security:
Zero Cloud / No Telemetry: Connects strictly through direct LAN, VPN, or custom addresses.
Hardware-Backed Encryption: All camera credentials, tokens, and broker secrets are encrypted at rest with Android Keystore.
App Lock: Optional biometric and PIN protection.
Cost: $0.99 (One-Time Payment, no subscriptions, no ads)
Hi everyone! 👋
I'm an indie developer and I just finished my first Wear OS watch face, **Troks Bubble Watch**. Google Play requires 12 testers to stay opted in for 14 days before I can release it publicly, so I'd really appreciate your help.
**What it is:**
- 50+ color themes, including 4-color combos (Sunset, Ocean, Neon, Retro…)
- 15 time fonts (Bebas Neue, Orbitron, Oswald, Share Tech Mono and more)
- Customizable complication slots + left/right side bars
- Animated "bubble lines" and flow bars
- 12/24-hour support
- Built with Watch Face Format, so it's light on battery
**How to join (takes 1 minute):**
1. Send me a DM with the email address you use on Google Play, and I'll add you to the beta
2. Once I confirm you're in, opt in to testing: https://play.google.com/apps/testing/om.troks.bubblewatch
3. Install it from Play Store on your watch: https://play.google.com/store/apps/details?id=om.troks.bubblewatch
4. Please keep it installed for 14 days 🙏 (you don't have to keep it as your active face)
**Requirements:** a Wear OS 4+ watch (Pixel Watch, Galaxy Watch 4/5/6/7/Ultra, etc.)
It's free and has no ads or data collection. Any feedback, bugs or feature ideas are very welcome. Comment here or DM me.
Thanks a lot ❤️
I have seen quite a few threads with people talking about how expensive or how poorly some iPhone to WearOS apps work.
I built my own to see if I can do it better.
Maybe I did, maybe not. Let me know what isn't great or what is missing.
For this initial release, it only depends on the bluetooth connection to send the notifications, so the feature set is read-only for now. It only transmits notifications from the iPhone currently but it lets your WearOS watch connect to both your Android and another iPhone at the same time. I built it initially so I can use my two phones at the same time and not miss iPhone notifications.
Apple has some new frameworks that would allow me to make sending messages back to the iPhone possible but it is currently EU only so I plan to add this once the US is supported as well.
Brief description: A Wear OS watch + Android phone app that uses heart-rate changes to prompt a check-in. You provide the context about what’s happening and how you feel, and can choose tools such as breathing, grounding, or journaling. Heart rate alone doesn’t identify an emotion.
I’m Keith, the founder. The attached video explains why I built it. I’m looking for Wear OS owners to help test watch/phone setup, check-in clarity, and how the prompts fit everyday life.
The planned beta runs December 1–31 for US adults 18+ with a compatible Android phone paired to a Wear OS watch. This is an interest list; enrollment is subject to platform approval.
If you’re interested, which watch and phone would you use? Feedback about confusing screens, setup issues, and prompts you’d dismiss is welcome.
I'm the indie developer behind **AV Wear Suite**, an app designed to solve a very specific itch: taking your personal music collection, audiobooks, podcasts, photos, and short videos directly to your **Wear OS watch** over local Wi-Fi, completely **offline**.
- **No cloud servers or accounts** (100% private, runs entirely on your local network).
- **No LTE / eSIM required** on the watch.
- **Smart compression:** Videos and photos are automatically optimized by your phone to fit watch screens and save storage space.
---
### Why I need your help:
To fulfill Google Play's closed testing requirements (keeping 12+ active testers for 14 continuous days) and guarantee rock-solid compatibility across different phone and watch manufacturers, I'm looking for **30 to 40 testers**.
- **Languages:** English, Spanish, German, French, Italian, Portuguese, Polish, Turkish, and Hindi (to help verify that strings and UI fit properly!).
### What the test involves (takes ~15 minutes):
Complete the short sign-up form so I can add you to the Google Play test track.
Opt-in on Google Play and install the app on both your phone and Wear OS watch.
Pair them over your local Wi-Fi and transfer a couple of songs, photos, or a video clip.
Keep the app installed for the **14-day testing period**.
Fill out a very brief feedback form at the end.
🎁 **Reward:** As a thank-you, all active testers will receive a **free lifetime promo code** for the full version upon public launch. (If you are also an indie Android developer running your own closed test, I'll happily test your app in return!).
*Privacy notice: Your email address is solely used to authorize your access on Google Play and will be deleted 30 days after the test ends.*
Thank you so much for supporting indie Wear OS development! Let me know your thoughts or questions in the comments!
I'm the indie developer behind **AV Wear Suite**, an app designed to solve a very specific itch: taking your personal music collection, audiobooks, podcasts, photos, and short videos directly to your **Wear OS watch** over local Wi-Fi, completely **offline**.
- **No cloud servers or accounts** (100% private, runs entirely on your local network).
- **No LTE / eSIM required** on the watch.
- **Smart compression:** Videos and photos are automatically optimized by your phone to fit watch screens and save storage space.
🌐 **Website & Screenshots:** You can see what the app looks like and explore its features at the website in the first comment.
---
### Why I need your help:
To fulfill Google Play's closed testing requirements (keeping 12+ active testers for 14 continuous days) and guarantee rock-solid compatibility across different phone and watch manufacturers, I'm looking for **30 to 40 testers**.
- **Languages:** English, Spanish, German, French, Italian, Portuguese, Polish, Turkish, and Hindi (to help verify that strings and UI fit properly!).
### What the test involves (takes ~15 minutes):
Complete the short sign-up form so I can add you to the Google Play test track.
Opt-in on Google Play and install the app on both your phone and Wear OS watch.
Pair them over your local Wi-Fi and transfer a couple of songs, photos, or a video clip.
Keep the app installed for the **14-day testing period**.
Fill out a very brief feedback form at the end.
🎁 **Reward:** As a thank-you, all active testers will receive a **free lifetime promo code** for the full version upon public launch. (If you are also an indie Android developer running your own closed test, I'll happily test your app in return!).
👉 **Sign-up Form (Google Forms, ~1 min):** in the link posted on the first comment.
*Privacy notice: Your email address is solely used to authorize your access on Google Play and will be deleted 30 days after the test ends.*
Thank you so much for supporting indie Wear OS development! Let me know your thoughts or questions in the comments!
Hello everyone, I recently bought myself a watch and it turned out that I am not in the countries where Gemini is supported, I have a question how can I turn it on without a VPN, I tried DNS but it did not work
Has anyone with a non-LTE Pixel Watch 5 received the Wear OS 7.1 update? I have not received it yet, and the manual update method has not been successful. My current build number is CP3A.260905.002, and I am interested in hearing about the experiences of other users.
Hi everyone! I've had the OnePlus Watch 3 for several months now and I'm generally happy with it, but sometimes when I'm doing sports it doesn't track the activity and I have to keep stopping and restarting.
I also think it's become a bit outdated, and some aspects of the interface don't quite do it for me. Would you recommend another option with Wear OS? Thanks!
We’re looking for 15 testers (plus a few reserves) for a Google Play closed test of a paid watch face.
Requirements:
Wear OS 5 or newer (e.g., Pixel Watch series, compatible Galaxy Watch with updates, OnePlus Watch).
Commitment: Keep the watch face active for 14 days, upload one screenshot from your watch daily, and leave a short review (battery, animations, design).
Starts: Monday, November 23.
What you get:
A free promo code for the watch face to keep.
$3 via PayPal after completing all 14 days.
Sign up here: Google Form (requires your Google Play email, watch model, and a software version screenshot).
A friend of mine is an indie developer and freediver who built a native freediving computer app for Wear OS that uses the watch's hardware pressure sensor underwater. We took it out for a shallow dive test-here's a quick clip of it running in the water:
Watch model shown: Samsung Galaxy Watch Ultra 2 (also supports Galaxy Watch 4 and above
Name of App: Freedive Ultra
Brief Description of app's features: Real-time depth & max depth using the watch's hardware pressure sensor, dive time & surface interval timers, automatic dive/surface detection, water temperature, dive speed, salinity calibration, and onboard dive logs.
Hi all, I'm a solo developer behind RadioShake, a free internet radio app on Google Play. I've built a standalone Wear OS version that streams straight from the watch over Wi-Fi or LTE, no phone needed.
Google requires 14 days of closed testing with real users before it can go public, so I'm looking for people with a Wear OS watch who'll use it for a couple of weeks and tell me what breaks.
What it does
* Browse stations by genre or country, or search
* Favourites and a sleep timer
* Now Playing tile for quick control
* Reopen the app mid-stream and you're straight back at Now Playing
Good to know: it plays through Bluetooth headphones (watch speaker support isn't there yet). Some stations are limited in the UK and EU.
Install RadioShake from the Play Store on your watch
Please stay opted in for the full 14 days. That's what counts for Google.
Bugs, ideas and "this annoyed me" all welcome, here or at [email protected]. I'll ship fixes during the test and credit what you find in the release notes.