BeeKing

Freelancers still bounce between a timer app, a project list, a spreadsheet, and a separate invoicing tool, so billable hours get lost between “I worked on this” and “I can send an invoice.” Mobile-first contractors especially need a single place where today’s timer, this week’s projects, and client-ready line items share one source of truth.

BeeKing targets that loop without forcing accounts or a cloud stack: log hours per task and day (including timers that survive app restarts), group work into projects, turn hours × rates into invoices for clients, and glance at analytics, all local on the device.

I built BeeKing as an Expo ~53 / React Native app with file-based Expo Router navigation: bottom tabs for Analytics, Tasks, Projects, and Invoices, plus stacks for create/edit flows and a settings area. Domain data lives in SQLite through Drizzle (tasks, task_history with timer fields, projects, project_tasks, clients, invoices, line_items); repositories and focused React contexts keep screens thin; Zod validates forms and settings.

The product differentiator is persistence and cohesion: running timers store start/pause/accumulated seconds in task_history so sessions survive relaunches; due dates schedule via expo-notifications when enabled; invoices compose line items from hours and rates; analytics use custom SVG hexagon/circle/line charts that match the honeycomb brand. Freemium Pro gating and a crown CTA are in the UI; payment providers remain intentionally unwired until store readiness.

Shipped surface includes task CRUD with search, bulk complete, archive, and N-day history; per-day task detail; project linking; client + invoice management with statuses (draft / pending / paid / overdue); analytics toggles across overview / tasks / projects / invoices; light/dark themes; currency and default hourly rate settings; side drawer and hexagon FAB chrome; and accessibility labels across interactive controls.

Architecture is repository + context over a Drizzle schema, with migrations at boot, seed scripts for empty DBs, toast feedback, and constraint-aware error handling documented for the data layer. I kept honesty in scope: import/export and PDF invoice export are stubs; Pro select only logs; help/privacy/rate-app actions are incomplete; categories/tags and a real bar chart remain on the checklist; bundle id is still com.anonymous.beeking with no EAS store config in-repo.

BeeKing is a substantial solo mobile MVP for local freelance time → invoice workflows: users can track and persist timers, organize projects, manage clients and invoices, configure reminders and preferences, and explore custom analytics, without a backend. The codebase is a coherent Expo product foundation, ready for PDF export, backup/sync decisions, real Pro billing, and App Store / Play packaging, and a clear portfolio piece for end-to-end ownership from naming and visual system through schema, UX, and domain logic.