Despite the issues with it and my own reservations, I’m considering switching to an iPhone for mic quality/FaceTime availability reasons.
What I’m unsure about though, is if I’d be able to develop an app or otherwise use the iPhone as a reverse proxy of sorts. I want my Pebble to be able to send requests through my iPhone (ideally using mTLS so the phone just forwards them) to another service. This way I can develop my own apps (mostly note taking/task management stuff) without needing to rely on anything on the phone itself.
Is this possible? I’m thinking I’d want the pebble to store requests and try when available, as well as being able to connect to other bluetooth endpoints (e.g. a Raspberry Pi when at home), so I can just open the app and the watch will send any batched requests.
It’s unfortunate the experience will be markedly worse on iPhones, but I think if I’m able to send requests to a service I host reliably (even if I need to batch/retry them and use other endpoints when available to avoid needing to keep iOS apps open all the time), then I think that’s enough for me.
Hey thanks for the response! And apologies for my late response .
I think my question is likely more suited for an iOS forum, but what I’m trying to figure out is if I’d be able to make an app that could essentially use iOS as a dumb tunnel (e2e encrypted from watch to server), and what the caveats might be for that (it seems like the pebble app or an app I create might at least need to be open).
Ahh, I think I’m just not aware of how the apps work well enough. Is one of these examples a good explainer? Or somewhere else in the docs?
My goal is to not send unencrypted requests from the phone, but instead for them to originate on the watch. Is that possible? I’m also worried about stability because of Apple’s (apparent) anti-competitive attitude towards other providers, as evidenced by the Pebble blog post.
Ah, the watch itself has no connection to the internet. The only contection it has to the outside world is a Bluetooth connection to the phone, that’s all. So you’d not be able to make web requests directly from the phone. Yeah those are good examples, there are also a couple guides walking you through the full process of writing an app on that site as well.
Ohh, got it. So I might need to send a request body over bluetooth for the app to forward then. I wonder if I can somehow package the whole request up . Anyway thanks for the discussion!
Yeah basically you can’t send a request directly, so you need te send whatever data you want in your request to the phone tdrough the app message system. Then in the phone’s JS code, you recieve that data, make a web request, then when you get back a response you send an app message back to the watch and have it do its thing.
.
all JS code is run on the phone, so all web requests are made from the phone.