Compose once, queue it, and let it publish across every social account you have connected.
One codebase, three targets.
The same Expo app runs on web, iOS and Android, against an Express API
that never stores a password because identity comes from Oxy.
|
A post moves through
|
One post targets several accounts at once. |
Bun workspaces, three of them:
| Package | What it is |
|---|---|
@schedio/frontend |
The Expo app. Expo Router, NativeWind 5, Zustand, i18next, and @oxy.so/bloom for tokens and primitives |
@schedio/backend |
The Express API. PostgreSQL/Drizzle repositories, validation, and the Oxy edge (CORS, security headers, rate limiting, auth) from @oxy.so/core |
@schedio/shared-types |
The DTOs both sides agree on. Compiled by postinstall, before anything else runs |
Sign in, sessions and user records come from the Oxy platform through @oxy.so/services in the app and @oxy.so/core on the server. Every protected route resolves its user with getRequiredOxyUserId from @oxy.so/core/server, so no user id is ever taken from the request body. See github.com/OxyHQ/oxy.
bun install # postinstall builds @schedio/shared-types
bun run dev # frontend and backend togetherOr one at a time:
bun run dev:frontend # Expo
bun run dev:backend # Express with Bun watch mode
bun run web # Expo straight to the browserYou will need Bun 1.4.3 and PostgreSQL 17. Environment variables are documented in the backend and frontend package READMEs.
Note
Schedio is a Bun workspace. Use bun, not npm or yarn: the root scripts are all bun run --filter, and the lockfile is bun.lock.
All workspace scripts
bun run build # every package
bun run build:shared-types
bun run build:frontend # static web export
bun run build:backend
bun run start:frontend
bun run start:backend
bun run lint # Biome check, then the frontend's Expo ESLint rules
bun run lint:fix # apply Biome's safe fixes and formatting
bun run format # Biome formatter only
bun run typecheck # tsc in every package that has a typecheck script
bun run clean # build artifacts and node_modulesPer-package scripts live in each package's own package.json. The frontend adds ios, android and web; the backend adds schema generation, migration and audited legacy-import commands.
What is in the app
Routes under packages/frontend/app/:
| Screen | Path |
|---|---|
| Dashboard | (main)/index.tsx |
| Composer | (main)/compose.tsx |
| Queue and calendar | (main)/queue.tsx |
| Analytics | (main)/analytics.tsx |
| Connected accounts | (main)/accounts.tsx |
| Post detail | (main)/post/ |
| Search | (main)/search/ |
| Profile | (main)/@[username].tsx |
| Settings | (main)/settings/ (appearance, language, privacy, profile customisation) |
| Sign in | (auth)/ |
The interface ships in English, Spanish and Italian (packages/frontend/locales/), and follows the system light or dark theme through the appearance store.
What is in the API
Routes in packages/backend/src/routes/: posts, queue, analytics, socialAccounts, profileSettings.
The eight first-party tables and constraints live in packages/backend/src/db/schema.ts. Existing source ids are preserved as text during import; new rows receive UUIDv7 ids.
Full endpoint documentation is in the backend README.
Issues and pull requests are welcome. Branch, change one thing, run bun run lint, open the pull request.