Samsung Galaxy Watch 5 Pro
- Thread starter Woody007
- Start date
You can dowload the Macro droid app on Wear Os but it cant do thaat much. It can only do stuff like activate a macro but it needs to be connected to the device for that. If you want to do more than you can dowload AutoWear. This app allows you to do stuff directly on your watch without needing your phone but you can also send information to macro droid using the plugin option.
It seems what you said "browser" was actually just an example of "a certain app" though, that's not important. Because...
EDIT: Yes, we can!
Performing UI interaction is not possible.
EDIT: Technically possible but not implemented yet in MacroDroid.
Last edited:
But please don't expect it would be very useful. It absolutely "works", but almost not usable even for just Googling something.
It seems useful when someone want to perform simple web requests, like controlling IoT devices while leave smart phone and go for a jog. And also any macros could be remotly triggered thanks to MacroDroid's webhook feature. I think many interesting personal things could be created if has basic knowledge to handle and program ESP8266-like devices or manipulate and relay data between APIs.
Ui interactions are possible:
Attachments
It's just "controllable" by the phone.
Watch to phone, phone to watch is possible. But not in the watch itself. As I told above I focused only on standalone use. Sorry but I don't think remote control could be mixed with automation.
I will correct wordings to be more accurate because that could be not true in absolutely. But that doesn't really make any sense from practical aspect too.
Attachments
You mean, UI interactions like tap are possible in the watch app itself?
I'll check the current API again and then correct if needed.
Yes, but only with AutoWear and not macro droid
Sorry for confusing with my incorrect claims! 
Now I see what I was missed and caused completely wrong assumption. It's shame that I was careless and my wordings seem unnecessarily assertive.
It took for a time because my last comment was written at almost 6 AM and then I had deep sleep. (Today is national holiday here!)
I think I have to study Wear OS API again.
Now I see what I was missed and caused completely wrong assumption. It's shame that I was careless and my wordings seem unnecessarily assertive.It took for a time because my last comment was written at almost 6 AM and then I had deep sleep. (Today is national holiday here!)
I think I have to study Wear OS API again.
If there's any action that can be done using Bixby Routines aka Modes and Routines, you can use this workaround to get it to work with MacroDroid.