Fantastic work you’ve done! This really proves the concept.One trade-off with the iPad/iPhone route is that device and the app need to stay on/running for the server to keep working. It is less “set and forget” than the Mac/Pi background-service approach and you’d need to keep the secondary device around. Both are valid depending on what you’ve got available.
But relying on a web server on another device seems a bit over complicated from a user perspective.
A proper iPhone/Android app would essentially be able to do the same thing without the need for the server. And a lot of what you’ve already done can be reused in that app.