Title: From my old Flask/Python web app to a real Flatpak desktop app (BookLibConnect) PT1
I’ve been running an audiobook manager/tracker as a Python + Flask web app for a while, and honestly… I’m tired of it being “a pile of scripts + a web UI” that I constantly have to babysit.
The old project was very “me” in style. I built a full theme system with CSS variables, instant theme switching (no reload), and I went a bit crazy with it:
- Dark Mode for night listening (my default)
- Winter Mode with a colder look, frosted-glass UI, and a subtle snow overlay/particles
- Cover-focused browsing, track lists, metadata workflow ideas, the whole “this is my personal library hub” vibe
It looked great, and the theme engine was fun to build… but maintaining it as a Flask web tool is just annoying long-term. Dependencies, browser weirdness, “is this running on the server / is it local / what broke this time”, and it always ends up feeling like a project held together with duct tape.
So I’m rebuilding it as an actual desktop app, packaged as a Flatpak.
New app name: BookLibConnect.
Goal: a clean local library manager that doesn’t need a browser, doesn’t need random setup steps, and can be installed like a normal app.
Current status (PT1):
- Set Library Root
- Rescan library
- Shows author/book + cover art
- Track list with file name, size, and modified date
So far I’ve only tested this on KDE Wayland (Qt: wayland). It’s early, it’s rough, and it’s nowhere near what my Flask app grew into, but it’s finally going in a direction that feels sustainable.
PT1 screenshot is attached.
If anyone here has practical Flatpak advice (Qt + Python, file access/portals, “don’t do it like this” warnings), I’m all ears.
For me, AI is useful for things that aren't important. For example, "I remember a song that had this theme, and here's a part of the lyrics. What song am I thinking of?"
It can (and has) even corrected my lyrics for me and found the correct song.
It did fail once, so I went back and 'corrected' it. It was not able to figure out that Sulloon and Ceylon were one and the same. (Both are prior names for Sri Lanka, with the former being more archaic than the latter.)
But, yeah... It's useful for stuff like that.

Reactions: PuppyHome