Original Summary

Hi everyone, I've been working on Collectarr , an open-source, local-first collection manager, and I'd love to find a few people interested in contributing, testing, or simply giving architectural/product feedback. GitHub: https://github.com/collectarr/collectarr-app Core backend: https://github.com/collectarr/collectarr-core Collectarr is an independent clean-room alternative to CLZ-style collection management . It is not affiliated with Collectorz.com / CLZ. The project is being developed independently, without using CLZ source code or proprietary assets. The idea is to build an open-source alternative around the workflows collectors find useful, while having our own architecture, implementation, data model, and room to evolve differently. What is Collectarr? The goal is to have one application for managing multiple kinds of collections without reducing every collectible to the same generic object. Collectarr currently supports 9 media kinds : Comics Manga Anime Books Games Board games Movies TV Music There is a shared library/workspace engine for common functionality, but each kind owns its domain-specific fields, metadata, editing experience, grouping/filtering behavior, and contained data where appropriate. For example, Music can model discs, tracks and credits, while Books, Comics, Games, Movies, etc. can have their own structures instead of being forced into a single universal schema. Some of the functionality The app is local-first and designed to remain useful offline. It includes things such as rich catalog metadata, personal collection data, multiple library views, filtering, grouping and sorting, smart lists, custom fields, images/covers, barcode workflows, bulk editing, import/export, collection statistics, duplicate detection, loans, and detailed media-specific editors. The architecture is split into separate projects: Collectarr App handles the personal library, local database, UI, editing and collector workflows. Collectarr Core provides the canonical shared metadata catalog, search and catalog administration. There is also an optional sync service for multi-device personal data. Tech stack The client is primarily: Flutter / Dart Riverpod Drift / SQLite go_router desktop + web + mobile targets The Core backend is: Python FastAPI SQLAlchemy PostgreSQL Meilisearch Redis The project is MIT licensed and currently pre-1.0 / beta. Why I'm posting here I've been doing most of the development myself so far, and the project has reached the point where additional perspectives would be genuinely useful. I'm especially interested in people who enjoy: Flutter / Dart UI/UX, desktop interfaces, responsive/adaptive layouts, reusable components, state management, performance and accessibility. Python / backend FastAPI, API design, PostgreSQL, search, metadata modelling and backend performance. Architecture Domain modelling, typed APIs, local-first applications, offline data, sync, large Flutter codebases and keeping shared infr

  • 情报分类：技术学习与提效
  • 分类依据：内容涉及技术、AI、软件工具或工程实践
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/13 02:06:52