u/SixteenFoxes

Hi r/TestFlight,

I’m the developer of SeenBox, a minimalist iOS app for tracking upcoming and currently available content directly from the Home Screen.

It’s totally free:

- No account

- No subscription

- No ads

- No data collection

- iCloud sync

SeenBox is intentionally simple: the main screen is focused on two things, upcoming and available, so you can see the status at a glance.

I’d really appreciate any feedback!

Hey everyone,

I’m pretty new to Notion and trying to figure out a good way to manage my solo app project there.

Right now I just use a basic Kanban board with backlog, todo, doing, and done. At work we use Agile with sprints, but for a solo project it feels a bit too heavy.

I mainly want a clean way to see what’s planned for the next update and also keep a history of completed tasks grouped by app versions/releases.

Curious how other solo devs or indie hackers organize this in Notion. Do you use some lightweight Agile setup or something completely different?

Thanks!

I am building a series tracking app and trying to design the cleanest and cheapest way to keep show, season, and episode metadata fresh over time. The app has two very different kinds of data: catalog data like series status, season and episode lists, air dates, next episode, posters, and so on from a provider like TMDB, and user-owned state like watchlist, watched episodes, paused, dropped, and completed status. My current instinct is that catalog data should be treated as a refreshable cache, while user state should be the real source of truth, and UI states like Upcoming, Available now, or waiting for next episode should be derived in the app instead of stored directly.

What is the best practical strategy for tracking metadata updates in this kind of app? If a user follows a lot of series, I probably do not want to fully refresh everything on every launch, but I also do not want stale episode dates or missing new seasons. Do people usually use TTL-based refresh rules, provider change endpoints, periodic full refreshes for tracked series only, or some combination of these?

Also, would CloudKit plus Core Data be a good fit for this use case if I want the simplest setup and very low ongoing cost, especially if I only sync user-owned state and keep catalog metadata as local cache?

I would love to hear how others have solved this in practice, especially if you have tried to keep infrastructure and maintenance as small as possible