I know that there’s an Assistant component in Thunkable for Android devices. It’s not clear to me if it’s still supported. But regardless, I’m trying to figure out how to have an “always on” voice recognizer for iOS. I thought about some sort of recursive function that starts listening and then in the “do” section, calls the function again. Saying “get air quality” would trigger the function to stop and evaluate the next word(s) spoken. I haven’t coded that part yet.
You made it a memory hungry app by taking a recursive approach.
If Thunkable uses the same memory block when you call the same function then it would be fine but if Thunkable request another memory block to execute the function it will not take long to get your phone memory clogged up by the same “start listening” function being called recursively.
Just an idea. I could be totally wrong. You can test it by introducing a wait block and say the magic word very soon to prevent memory clogging up.
