Files
Bike-Tinder/docs/HOW-IT-WORKS.md
2026-11-18 00:40:21 -04:00

1.7 KiB

How Bike-Tinder works

From classifieds to cards

The motorcycle-hunt crawler collects Kijiji listings in Nova Scotia and New Brunswick. The importer reads the crawler's snapshots, adds new listings, updates existing ones, and retires listings only after repeated misses. A blocked or failed fetch isn't proof that a listing is gone. See Sources and the data model.

The web app reads that catalog from SQLite and presents listings in a swipe deck or a searchable List. Your current verdict is editable; the app also records swipe events for ranking. Tap the sides of a deck card to browse its photos, the center to open the details, or the photo in the details view to open the fullscreen gallery. See the interface spec for gesture and keyboard behavior.

Ranking and photos

With no swipe history, the deck starts with the motorcycle hunt's scoring rubric. Once there is history, the app builds a taste profile and uses it when ordering future batches. Batches can mix fresh bikes, wildcards, and second looks. A model runs outside the swipe path: the swipe itself never waits for a model response. See Ranking and Design.

The importer retains gallery URLs in source order. The running stack keeps primary photos locally; when a requested gallery photo isn't cached, the app redirects to the source image. A missing photo uses a placeholder. See the gallery mirror backlog.

More detail

Development and deployment covers setup and testing. The roadmap and backlog cover planned work.