Hope you read the previous part of the departure board. Else check the pictures. ;) -- So I think that the departure board was OKAY, and I kept there. But the reality was that it also needed to be improved a lot. Energy consumption, component quality stress, fragility, versatility, UTILITY. I must highlight again that I have "recovered" this screen from a laptop, then I bought a frame kit from Aliexpress. I remember that the frame was really expensive but was precise. It offered a very tiny room for the Raspberry, which I thought it could actually burn the display, but that didn't happened. The display can support a lot of heat apparently. The deployment started to be really important, since every iteration you could emulate sure, but then eventually it must be added to the device like several times per minute. I have created few scripts for versatility. I have found problems with the browser. At the begging I was using chromium, which opened with an...
Thinking on music playback experiences, I always would have love to have Kazaa, iMesh or Ares to be more like this; where is also the default player. I think that since the download was not required anymore on the obscure era of the streaming services, we as user lost the sense of having the required structure. Also we lost our span attention making me wonder... Who are the ones really using those IRC channels on Ares? hahaaha Anyway this week I've been doing a research called NicotineD. It's a mix with Nicotine and Navidrome where the integration should be great to get the simplicity of the streaming service, the database of a well stablished global network, the privacy and discretionality of self hosted. I'm trying to understand what this user might want, how to present the results, how to deal with integrations and make it as zero click as possible. Take a look at https://github.com/kevinch3/NicotinD