From read-only list to collection command center
The mobile portfolio was a read-only list of what you own. It told you card names and counts, and that was about it. You could not filter, sort, select, or do anything with the holdings. Every management task bounced you to the web app.
That changed this weekend. Binderdex mobile now has a proper portfolio command center: exact card-variant and sealed holdings, compact performance context, web-parity filters and sorts, persistent display preferences, selection and bulk management, and bounded CSV export.
Bulk operations that do not blow up
The tricky part of a bulk-edit feature on a phone is not the UI. It is making sure you cannot accidentally wreck a collection with a fat-finger condition change on 200 cards at once. A few constraints that matter:
- Cap at 250: bulk mutations are capped at 250 items with bounded concurrency, so a select-all on a huge collection cannot queue thousands of writes.
- Reject mixed conditions: if you select 50 cards in varying conditions and try to bulk-set them all to NM, the API rejects it before touching anything. No silent partial writes.
- Export cap at 20,000: CSV export omits PII and internal row IDs, and spreadsheet formulas are escaped. You get a clean spreadsheet, not a data leak.
One attribution bug, one fix
Separate commit, same day: the analytics provider was returning a complete noop whenever PostHog was unavailable, which silently suppressed AppsFlyer and Statsig too. One unset key killed three tracking destinations. Now each destination fans out independently, and the first post-install activation KPI (collection_card_added) fires at the shared add-card surface across every entry point.