My kids have a few podcasts that they love to listen to, but they were unable to use their Yoto players to listen to them so they often had to use the smart speakers in the house, or would need us to play them on the radio in the car.
It was possible to manually download episodes and then construct a Yoto Make-Your-Own (MYO) playlist, but we had to keep coming back to it every time a new episode was released.
This was my first attempt at vibe-coding something from scratch. I've got a few decades of programming experience and strong opinions about the "right" way to do things, but I did my best to let it handle everything (though I did guide it to pick tech my preferred tech). It was able to essentially one-shot an implementation from the initial requirements which was impressive. After that I started adding features for my own QoL (UI improvements, multiple podcasts on a single playlist, etc.)
The majority of the work that I did was creating and managing credentials, and guiding it through what my home-server config looked like to make it easy for me to deploy.
All-in-all, very satisfied with the result. It makes my kids and wife happy, and saves us some time. I'm glad I was able to accomplish this and didn't need to spend much time hacking around with auth systems and figuring out auto-reconnect schenanigans, but it does feel a little empty inside. Hopefully someone else will find this useful as well and that'll make it up to me!
My kids have a few podcasts that they love to listen to, but they were unable to use their Yoto players to listen to them so they often had to use the smart speakers in the house, or would need us to play them on the radio in the car.
It was possible to manually download episodes and then construct a Yoto Make-Your-Own (MYO) playlist, but we had to keep coming back to it every time a new episode was released.
This was my first attempt at vibe-coding something from scratch. I've got a few decades of programming experience and strong opinions about the "right" way to do things, but I did my best to let it handle everything (though I did guide it to pick tech my preferred tech). It was able to essentially one-shot an implementation from the initial requirements which was impressive. After that I started adding features for my own QoL (UI improvements, multiple podcasts on a single playlist, etc.)
The majority of the work that I did was creating and managing credentials, and guiding it through what my home-server config looked like to make it easy for me to deploy.
All-in-all, very satisfied with the result. It makes my kids and wife happy, and saves us some time. I'm glad I was able to accomplish this and didn't need to spend much time hacking around with auth systems and figuring out auto-reconnect schenanigans, but it does feel a little empty inside. Hopefully someone else will find this useful as well and that'll make it up to me!