Bobby by Rebble
There’s a new watchapp on the Rebble App Store!
Go check it out in the App Store!
Diorite screenshots:
Basalt screenshots:
2 Likes
For anyone who may be unaware, bobby DOES work on the new Pebble app by Core Devices (coreapp), despite what the description says. You do need a Rebble subscription to use it still.
1 Like
This only applies to Android though, correct? I went back to using the OG Pebble app in part to have access to Bobby, but my understanding via Discord is that it still isn’t functional on iOS. Am I wrong on this?
1 Like
I have a Core2Duo and IOS and the new app. I can get past the “allow” question by using the settings page on the phone, and Bobby understands and captures my voice, but never asks for or gets a response, so no, it’s not quite working yet on IOS
1 Like
I appreciate the response. I was bouncing between the Core app and OG app for awhile, but I got tired of reorganizing my watchfaces and decided to stick with the OG for now, but I’d really like to get back to the Core app, as I had much better stability with Bluetooth, and I get more battery (on the watch side AND the phone side) with it as well, but I don’t want to sacrifice the functionality, either.
First-world problems, I suppose. 
1 Like
I bought a subscription. But it still doesn’t work.
1 Like
Hey! Few questions for you:
- Are you on iOS or Android?
- Are you using the new orange Pebble Core app, or the legacy grey Pebble app?
- What watch do you have?
1 Like
iOS, new orange app, pebble 2 duo
1 Like
Bobby doesn’t work on Core app on iOS yet unfortunately, only on Android
1 Like
Ah, yep. Websockets aren’t working in the Core app for iOS yet - there are a handful of other watchapps having trouble with the same. Bobby won’t work on iOS until those are fixed.
If you’d like a refund for your subscription before then, feel free to reach out to support@rebble.io over email
1 Like
Is there a roadmap/timeline/milestone/objective term of your choice for when iOS support might appear?
This should really be stated in the “compatibility” section of all of the marketing materials that mention Bobby.
1 Like
Will we always need a Rebble subscription in order to use Bobby?
Yes, Bobby requires us to pay for the tokens that our users use while using it. We don’t have any other way to fund its use otherwise.
1 Like
iOS support is blocked by an incomplete websockets support in the Core app. We are hoping that Core fixes it at some point, since it doesn’t only affect us, but also other developers on the platform.
1 Like
Yeah, to add to that, Bobby would actually be our single most expensive feature if every active user used it. (Weather is a close second! But that’s a fixed cost – we pay for a fixed number of requests up front, rather than by the request.)
LLMs are really expensive to run. Anyone who is giving you free LLM access is either losing money (and therefore is not going to be around for the long term), or is making money some other way (usually, by selling your data). We don’t want to do either of those, so I do not expect to provide free access to LLMs for the foreseeable future.
But I do agree that probably we should mention that iOS+CoreApp is busted.
1 Like
Updates for Bobby’s back end today! A few quickies.
There was a bug where Bobby was eating quota way quicker than it should have (input and output token costs were swapped – oops!). This wasn’t really a problem before, but the upgrade to Gemini 2.5 made it quite a bit more expensive, and meant that even routine usage of Bobby would burn through all your quota pretty quick. I fixed that, and I also reset everybody’s quota for the month of February.
(While I was in there, I also updated the quota calculations to account for context caching, which should hopefully improve matters at some point in the future once I … figure out how to enable context caching.)
I also made a few tweaks to the system prompt (sometimes Bobby would send feedback when it shouldn’t, and I tried to convince it not to, hopefully; I updated the knowledge cutoff; and @jfonte tweaked the system prompt to be a little better at translating, hopefully).
Mostly small things, but the changes are now live – let me know if you see any issues!
1 Like
I noticed that for dictation, the microphone is active for about 10 seconds. My commands are usually just one word like Weather, then I have to wait 8 or 9 seconds. Can there be a 3 or 5 second setting to shorten the process?
Hey! The dictation screen is part of the PebbleOS system, and not controlled by the app. Some watches are better than others about detecting when you’re finished speaking.
In the meantime, to finish a dictation session early, you can press the Select button again once you’re done talking. Hope that helps!
1 Like
Yes, that helps a lot, thanks!
1 Like
