# ⛽ I Built a Cross-Platform Fuel Finder with React & Supabase: The Indie Dev Journey
An indie developer created a cross-platform fuel finder app using React and Supabase to streamline the process of locating fuel stations during road trips. The app features fuel logging, trip cost estimation, and multi-country support, all while avoiding high costs associated with Google Maps. The developer shares insights on the challenges faced and lessons learned throughout the development process.
- ▪The app was built using a tech stack that includes React, TypeScript, Tailwind CSS, and Supabase.
- ▪It utilizes OpenStreetMap and the Overpass API to fetch nearby fuel stations without incurring high costs.
- ▪The app includes features like fuel logging, trip cost estimation, and adapts to different units and currencies based on the user's location.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/jicoing/-i-built-a-cross-platform-fuel-finder-with-react-supabase-the-indie-dev-journey-2aom |
| Publication time | Sat, 23 May 2026 08:53:46 +0000 |
| Retrieval time | 2026-05-23T09:07:26.171Z |
| Last seen | 2026-05-23T09:07:26.171Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | EMj6MhjmpHjy |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 503381) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } jicoing Posted on May 23 # ⛽ I Built a Cross-Platform Fuel Finder with React & Supabase: The Indie Dev Journey #react #showdev #sideprojects #webdev As someone who loves long road trips, I was tired of switching between five different apps to find a station, log my mileage, and calculate if I actually had enough cash for the next leg of the trip. So, I did what any dev does... I built my own.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
