Rixin Archive
Local-first Android archive for scattered work files
What is Rixin Archive?
Rixin Archive is a local-first Android document organizer for people who receive work files through chat apps, office suites, browsers, downloads, and file managers. Contracts, quotations, spreadsheets, PDFs, project photos, and meeting records often stay scattered across WeChat, QQ, WeCom, DingTalk, WPS, browser downloads, and separate media folders. Rixin Archive turns that scattered collection into a searchable local archive.
The core workflow is intentionally direct. Users share or open a supported file into Rixin Archive, choose an archive box, and save a copied local version while preserving the original file extension. The app does not depend on the original file remaining in a chat cache or download folder. Archived items can carry useful retrieval context such as a clearer filename, document type, source app, project, organization, amount, location, tags, notes, and custom dimensions.
The optional AI Archive Assistant can read supported documents, PDFs, and images and propose a concise content-based title, summary, tags, and filing fields. It is not enabled by default. Users review and edit suggestions before archiving, or file manually without AI. Search combines ordinary keywords, structured filters, and optional fuzzy matching, making it possible to find files by name, notes, extension, date, archive box, source app, tags, project, organization, amount, and custom dimensions. Batch import and batch actions help organize existing collections.
Archived copies, summaries, dimensions, and search indexes are stored locally on the device by default. Core filing features are free with ads, and an optional Pro subscription is available through Google Play.
Ready to launch?
Submit your product and get discovered by builders and creators worldwide.
Launch Now
FounderPlaybooks.
What other founders did to grow.
2722 dispatches from hundreds of founders, pulled from the week's best podcasts.
the big launch philosophy has been one of like the great mistakes of my career... for me it's definitely fear right is like oh I don't want to... I'm not going to show this to the world because I need this one little extra thing otherwise people are going to ignore me.
Holding Features for a Big Launch Is Fear Dressed Up as Strategy
David spent four years bundling Weather Up 3.0 features — Apple Watch app, widgets, interactive widgets — waiting until it felt big enough to launch. What felt like strategic packaging was really delay rationalized as planning. During that time downloads dropped to 15 a day, the app fell out of Apple feature rotations, and he was funding it personally. The subscription model removed every incentive to hold features back; he just never updated his mental model to match.
any feature that makes this easier is a strong candidate to be built early so for inputs just look for features that add ways to connect and make connection easier to the things that come before and for outputs add new formats that follow-up tasks expect or can deal with more easily
Prioritize features that improve workflow inputs and outputs over standalone ones
Your tool lives inside a chain of other tools — what comes before, what comes after. Features that improve the join between your tool and the upstream/downstream steps compound the most. Import filters and integrations for inputs; new export formats (SRT subtitles, CSV, API webhooks) and enrichments for outputs. Standalone bells-and-whistles that don't touch the workflow boundary almost always underperform integrations.
There's a play for whatever you're stuck on.
Read all 2722 playbooks