How malasadongegg/lapagkainan works
LapagKainan is a community-powered Filipino food discovery map backed by a REST API. A user searches or browses spots, opens a spot’s community details, and can contribute a discovery, visit, review, or other activity; the app sends those actions to the API, which applies domain rules and persists data. The map, discovery feeds, profiles, saved spots, and admin moderation are distinct product branches. The README and source index establish the broad API capabilities; some server routes and frontend screens were not excerpted, so those relationships are shown only where documented.
Main entry points: api.ts API client · index.js REST API · App.tsx App shell · MapScreen.tsx Map search
Components 23
Discovery client
- App shell
web/src/App.tsx - Map search
web/src/screens/MapScreen.tsx - Interactive map
web/src/components/MapView.tsx - Discover and profiles
web/src/screens/Screens.tsx - Spot details
web/src/components/SpotDetail.tsx - Community stories
web/src/components/stories.tsx - Location and geocoding
web/src/lib/geo.ts - Map tiles
web/src/lib/mapTiles.ts - Display formatting
web/src/lib/format.ts
Community contributions
- Contribution flows
web/src/components/flows.tsx - Auth and dialogs
web/src/components/dialogs.tsx - Shared UI and icons
web/src/components/ui.tsx
API and domain
- API client
web/src/lib/api.ts - Product data types
web/src/lib/types.ts - REST API
server/index.js - Spot search and lifecycle
server/spots.js - Auth and request utilities
server/util.js
Operations and data
- Admin and moderation
server/admin.js - Admin dashboard
web/public/admin.html - SQLite data store
server/db.js
Other components
- Diner
- CARTO tile service
- Nominatim geocoder
Connections 32
- Diner → App shell: uses
README.md - App shell → Map search: shows map
web/src/App.tsx - App shell → Discover and profiles: shows feeds
web/src/App.tsx - App shell → Auth and dialogs: opens auth
web/src/App.tsx - App shell → Contribution flows: starts discovery
web/src/App.tsx - Map search → API client: fetches spots
web/src/screens/MapScreen.tsx - Map search → Interactive map: renders map
web/src/screens/MapScreen.tsx - Map search → Location and geocoding: gets location
web/src/screens/MapScreen.tsx - Interactive map → API client: loads map data
web/src/components/MapView.tsx - Interactive map → Map tiles: uses tiles
web/src/components/MapView.tsx - Map search → Spot details: opens spot
web/src/screens/MapScreen.tsx - Spot details → API client: loads interactions
web/src/components/SpotDetail.tsx - Spot details → Contribution flows: starts review
web/src/components/SpotDetail.tsx - Spot details → Community stories: shows stories
web/src/components/SpotDetail.tsx - Discover and profiles → API client: requests feeds
web/src/screens/Screens.tsx - Contribution flows → API client: posts contributions
web/src/components/flows.tsx - Contribution flows → Location and geocoding: verifies location
web/src/components/flows.tsx - Auth and dialogs → API client: authenticates
web/src/components/dialogs.tsx - Shared UI and icons → API client: loads photos
web/src/components/ui.tsx - API client → REST API: calls REST
README.md - Location and geocoding → Nominatim geocoder: geocodes places
web/src/lib/geo.ts - Map tiles → CARTO tile service: loads basemap
README.md - REST API → Spot search and lifecycle: queries spots
server/index.js - REST API → Admin and moderation: routes admin
server/index.js - REST API → Auth and request utilities: checks requests
server/index.js - REST API → SQLite data store: reads and writes
server/index.js - Spot search and lifecycle → SQLite data store: queries lifecycle
server/spots.js - Spot search and lifecycle → Auth and request utilities: uses geo helpers
server/spots.js - Admin and moderation → SQLite data store: manages records
server/admin.js - Admin and moderation → Spot search and lifecycle: manages spot state
server/admin.js - Admin and moderation → Auth and request utilities: uses utilities
server/admin.js - Admin dashboard → REST API: uses admin API
README.md