The tool I wanted didn’t really exist
Every social media scheduling tool seems to assume the same thing.
You should create an account.
You should connect your platforms.
You should trust a cloud backend.
You should pay monthly.
You should automate your workflow.
That model makes sense for agencies, teams, and larger content operations.
But for me, it always felt like too much.
I didn’t want another dashboard.
I didn’t want another subscription.
I didn’t want unfinished drafts sitting on someone else’s server.
And I didn’t want every post to become an automated pipeline.
I just wanted a quiet place to think before publishing.
That idea eventually became Skedoff.
I thought I was building a scheduler
When I started, I thought I was making a lightweight social media scheduler.
Simple. Minimal. Functional.
Something that would help me draft captions, keep post ideas organized, and maybe make content consistency a little easier.
But somewhere during the process, I realized I wasn’t actually trying to “schedule” in the usual sense.
What I really wanted was a boundary.
A little bit of distance between writing something and immediately publishing it.
That gap matters more than people admit.
Sometimes the best thing a tool can do is not help you post faster.
Sometimes it should help you pause.
That changed the entire direction of the app.
What Skedoff became
Instead of building another all-in-one social media manager, I built a manual workflow tool.
Skedoff is a privacy-first, offline-first social media content planner for creators, freelancers, small businesses, and personal brands who want to prepare posts without giving up control.
It doesn’t connect to your social accounts.
It doesn’t auto-post.
It doesn’t upload your drafts to a developer-managed server.
You write your content offline.
You tag the platform.
You move it through a simple workflow.
Then when you’re ready, you open the real platform and post manually.
That’s it.
And that simplicity is the point.
The product philosophy
Skedoff was built around a few constraints that I wanted to keep non-negotiable:
- No account required
- No app cloud sync
- No monthly subscription
- No auto-posting
- No analytics or tracking
- No “growth dashboard” pretending to be productivity
I wanted something that respected the private, unfinished nature of drafts.
A draft is often more personal than a published post.
It’s where ideas are messy.
Where tone is uncertain.
Where you test wording, timing, and intent.
That kind of content should not automatically become platform data.
The workflow is intentionally small
Skedoff is built around a simple three-stage flow:
- Draft — where ideas begin
- Queue — where ready posts wait
- Published — a local record of what went live
In other words:
Draft → Queue → Published
That’s the whole model.
Not because I couldn’t add more.
But because too many tools become bloated by trying to solve every adjacent problem.
For this app, I wanted a workflow that stays clear and stays honest.
Why offline-first matters here
“Offline-first” gets used a lot as a technical buzzword, but in this project it’s also a product decision.
Skedoff is intentionally designed to feel like it belongs on your device.
Not in a browser tab.
Not in a remote workspace.
Not behind another login screen.
That means:
- You can draft without internet
- Your content stays local
- There’s no dependency on a hosted backend
- The app remains usable even when you’re disconnected
For a social media planner, that may sound counterintuitive.
But I think that tension is exactly what makes it useful.
Publishing is online.
Planning doesn’t always need to be.
The current build status
Right now, Skedoff is at a stage that every indie developer knows:
technically done, emotionally still in review.
The core pieces are in place:
- UI done
- Local database done
- Core Draft → Queue → Published flow working
- Platform tagging working
- Search and filtering working
- Android build prepared
And as of now, the app has been submitted to Google Play for review.
If everything goes smoothly, it should be live in roughly 3–5 days, which is a pretty normal window for a first app release (though Google can always surprise you).
That waiting period is strange.
There’s always a gap between “it works” and “I’m ready to let strangers use it.”
I’ve been in that gap for a while.
But shipping matters more than polishing forever.
Some technical notes
Skedoff is built with Flutter, with a local-first approach and a deliberately simple architecture.
A few design choices mattered a lot:
- Local database first instead of a cloud backend
- A focused three-tab UX instead of feature-heavy navigation
- Minimal friction in the writing flow
- Platform tagging without requiring integrations
- A product model built around manual publishing, not API automation
That last one is important.
It would have been tempting to chase auto-posting, account connections, or “smart” scheduling features.
But I think that would have broken the core idea.
The goal is not to replace the social platforms.
The goal is to give creators a cleaner place to prepare before entering them.
What comes next
Version 1 is intentionally narrow.
I wanted to validate the product philosophy before adding more layers.
The next steps I’m considering:
- Local notification reminders for queued posts
- Bulk actions for faster content management
- Small UX refinements based on real usage
- Better export and backup thinking
- Possibly optional, privacy-respecting crash reporting in the future
The challenge from here is not just feature development.
It’s discipline.
A lot of products become less useful because they slowly become everything.
For Skedoff, I want to protect the original boundary:
- offline-first
- privacy-first
- manual by design
- simple enough to stay trustworthy
Why I care about this project
Skedoff is not trying to be a huge platform.
It’s a small app with a small promise.
And I think there’s still room for software like that.
Not every tool needs to be a service.
Not every draft needs to be uploaded.
Not every workflow needs to be optimized into automation.
Sometimes good software just helps you do the work — and then gets out of the way.
That’s what I want Skedoff to be.
Follow the project
If you want to see the product page or follow along:
- Skedoff: https://flagodna-developer.github.io/skedoff/
- My site: https://www.cahyanudien.site
I’m Cahyanudien Aziz Saputra, building under FlagoDNA.
Skedoff is currently under Google Play review, and if all goes well, it should be live soon.
Plan offline. Post when ready.
