Well, I'd suppose if this becomes a web standard, it will come with an eventually stable API. And I wholeheartedly vote for "write a (lovely) webpage that still functions in a decade" over "write an app that might be (breaking) with the next generation of mobile phones (API changes, new OS,...)". Especially if I build any of that myself, and instead have some closed, physical thing I bought which depends on an external controller.
(parent can replace the "" with whatever he likes, but since I find swearing doesn't quite fit HN, I've put some more appropriate terms next to them)
(parent can replace the "" with whatever he likes, but since I find swearing doesn't quite fit HN, I've put some more appropriate terms next to them)