ProjectsSeptember 8, 2025

Daily Planner App

Daily Planner

Introduction

Daily Planner is an Expo (React Native) application that lets a signed-in user create, view and manage scheduled tasks with time ranges, optional reminders, repetition rules and tagging. Authentication is handled through Better Auth with a Prisma-backed data store. The same codebase serves API routes (for auth and tasks) and the mobile/web client. Local SQLite (via Prisma) is used in development; a LibSQL/Turso database can be enabled in production through environment variables.

Features

User authentication (email and password) via Better Auth
Session handling using secure tokens or cookies (API routes)
Create, read and update tasks with start and end timestamps
Support for all‑day tasks and status (pending, in progress, completed, canceled)
Task priority levels and optional color labeling
Reminders with configurable minute offsets and delivery method placeholder fields
Basic recurrence support through repeat rules (frequency, interval, until, count)
Tagging system (user‑scoped tags) and participant relationships
Simple tasks API (fetch by date, create, update) under app/api/tasks
React Native UI components styled with NativeWind and Gluestack UI
Environment‑driven selection between local SQLite and LibSQL adapter

NOTE Current master branch may have breaking changes detach to commit 9ec40a5a5ea77994056dc451c0533baec95e249e when working / using the app

TODO

The current app structure acts as a monorepo to bundle the server into a web compoenent outside of expo's android/ios build. The problem is that prisma depends on node:fs runtime which is not currently supported in EAS hosting, As a result I have to refactor the whole thing to a cloud build which does not depend on node:fs. I have tried uploading the dist to netlify, hosting on vercel, and even switching to turso + libsql for an entire overhaul on the system. All current implementations just point to use a different backend schema that does not depend on prisma. So i will have to do:

Remove prisma implementation

check expo-sqlite feasability for better-auth

Refactor backend to make calls to server (hono-ts) if expo-sqlite does not work out

Refactor logic to work on only cloud / only local build based on option 2

🚀 How to use

npx prisma generate

For a production deployment set the following (example for Turso / LibSQL):

TURSO_DATABASE_URL=... # only on the server host
TURSO_AUTH_TOKEN=...   # only on the server host
EXPO_PUBLIC_AUTH_BASE_URL=https://your-production-domain

Then run migrations against the remote database:

npx prisma migrate deploy

The mobile client will talk to the deployed API at EXPO_PUBLIC_AUTH_BASE_URL/api/auth and .../api/tasks.

Recent projects

The Eden Project

What if music wasn't so inaccessible..

Read case study

Run over a Deer

A Silly little game based on the hit movie Over The Hedge

Read case study

Just a Walkthrough

Framework-agnostic onboarding walkthrough / product tour library with optional React provider & Tailwind/shadcn support.

Read case study

Suvan GSgreeenboiGreenArcadeSuvan GSgreeenboiGreenArcadeSuvan GSgreeenboi