Why I Turned My Minimalist Calendar into an End-to-End Project & Developer Workspace

Hey Indie Hackers and my friends.

A few months ago, I launched Oria as a fast, privacy-first personal planner for routines, shifts, and time tracking. But as a solo builder running multiple client projects and side products, I hit a familiar wall:

My schedule lived in one app, my tasks were scattered in Notion/Jira, my API credentials were lost in messy .env text files, and tracking project budgets felt like a chore. Switching between 5 different browser tabs just to finish a client milestone was killing my focus.

So over the last few weeks, I completely rebuilt the Business Workspace in Oria. The goal was simple: bring project delivery, team collaboration, and developer tooling into one cohesive workflow without bloating the interface.

Here is a look at what went into the new Project Hub & Developer Hub, and how it transformed Oria from a daily planner into an execution machine.

1. Project Hub: From Rough Idea to Shipped Feature

Most project management tools force you into one rigid framework. In Oria, we designed the Project Hub around the actual lifecycle of indie projects:

Interactive Kanban & Smart Deadlines: Bidirectional card movements with single-tap status advancements. Cards automatically prioritize based on upcoming deadlines, and custom badge constraints prevent visual clutter even with multiple tags, sections, and milestones.
Sprint Phases & Roadmaps: Group deliverables into sprints or multi-stage release phases. You can search, assign, and track unassigned tasks into specific phases in seconds.
Live Budget Burn & Expense Tracking: Real-time spending progress versus planned budgets with localized currencies, keeping client expenses transparent before you overrun.
Project Canvas: A full Markdown specification workspace with clean dismiss controls, distraction-free editing, and direct authenticated share links for stakeholders.

2. Developer Hub: The Missing Toolbox for Technical Founders

As technical builders, we constantly juggle secrets, test endpoints, and document API flows. Opening a separate desktop client for quick tasks slows down flow state.

Inside Oria, the Developer Hub puts essential utilities right next to your projects:

Secrets & Environment Manager: Securely organize .env variables and third-party tokens with zero-knowledge local storage. Sensitive secrets are automatically stripped and sanitized during backups.
API & Webhook Playground: Craft requests, inspect response payloads, and generate copy-ready cURL commands directly within your project context.
Code Snippet Vault: Store reusable shell scripts, SQL queries, and architectural boilerplates tagged by language and project.

3. Team Collaboration & Zero-Leak Access Control

Solo founders often grow into lean agencies or collaborate with freelancers. We redesigned the permissions engine in Oria with strict privacy boundaries:

Multi-Assignee Architecture: Tasks can be assigned to multiple teammates, entire functional teams (e.g., Core Team, Mobile Team), or both simultaneously.
Strict Project Isolation: Private projects remain strictly visible only to their owner. Team projects are securely accessible only to active direct members or assigned workspace teams—preventing accidental data leakage across shared workspaces.
Contextual "My Tasks": The task view dynamically filters only the projects and teams where you actually have assigned deliverables, eliminating workspace noise.

4. Under the Hood: Building for Speed and 14 Languages

Offline-First with Cloud Sync: Personal routines and calendars work completely offline on-device, while Business projects synchronize seamlessly across Web and Mobile.
Full Native Localization: Every date picker, milestone selector, and budget tracker is localized natively across 14 languages (English, Turkish, German, Spanish, French, Japanese, Korean, Arabic, and more).

What’s Next?

We just rolled out this major update on both iOS and Web. You can check it out here: Oria.

I'd love to hear your feedback:

What is the single biggest friction point in your current project/task workflow?
If you are building solo or running a small team, what developer tools do you wish were built into your daily workspace?

Drop your thoughts below—happy to answer any technical questions about the architecture or product decisions!