DEV Community: Cahyanudien Aziz Saputra

HadisKu Is Now on Windows, Linux, and Android — and It's Completely Free

Cahyanudien Aziz Saputra — Fri, 03 Apr 2026 17:27:34 +0000

Version 3.0.0 is the biggest release yet: multi-platform, no ads, no subscriptions, and new Arabic search built for serious study.

HadisKu started as a simple Android app. One goal: make hadith accessible. Today, with version 3.0.0, it's something meaningfully different — a free, multi-platform hadith reader available on Windows, Linux, and Android, with nothing standing between you and the text.

What is HadisKu?

HadisKu is a free, open-source app that brings together authentic hadith collections from 14 major Imams in one place. It's designed for reading, searching, and studying hadith — lightweight, focused, and distraction-free.

HadisKu is developed by Flagodna — a developer focused on building purposeful, open-source applications. Learn more at https://flagodna.com.

Available now on three platforms

For the first time, HadisKu runs on desktop. Whether you prefer studying from your phone on the commute or from your laptop late at night, v3.0.0 meets you wherever you are — Windows, Linux, and Android.

What's new in v3.0.0

This release is available to download right now. Here's everything that changed:

Added

Arabic text search — find hadith by searching directly in Arabic script across all collections
Hadith display order settings — choose Arabic → Indonesian or Indonesian → Arabic, based on your preference
Arabic text alignment options — left, right, or justify, however you read best

Changed

New app icon with a fresher, more representative design

Improved

All ads removed for a cleaner, uninterrupted reading experience
All in-app purchases and subscriptions removed — HadisKu is now completely free

A quieter, more focused experience

The decision to go fully free reflects what HadisKu is actually for. Reading and studying hadith is a contemplative practice. Ads break that. Paywalls break that. Starting with v3.0.0, none of that exists anymore — just you and the collections.

About the developer

HadisKu is built and maintained by Cahyanu Dien, an independent developer passionate about creating meaningful open-source tools. You can follow his work and read more on his personal blog at https://www.cahyanudien.site.

The app is developed under Flagodna — visit https://flagodna.com to learn more about the team and their other projects.

Try it or follow development

v3.0.0 is released and ready to download now:

Google Play Store: https://play.google.com/store/apps/details?id=com.flagodna.hadisku
GitHub: https://github.com/Flagodna-Developer/hadisku
Download v3.0.0 (Windows & Linux): https://github.com/Flagodna-Developer/hadisku/releases/tag/v3.0.0
Flagodna: https://flagodna.com
Developer Blog: https://www.cahyanudien.site

Thank you to everyone who has used HadisKu, shared feedback, and supported the project. This release wouldn't exist without you.

FlagoDNA: From Nature's Inspiration to Our Brand Identity

Cahyanudien Aziz Saputra — Fri, 03 Apr 2026 14:54:51 +0000

Every brand has a story. FlagoDNA was born from a deeply personal moment of reflection — one that would shape everything we build.

It started with a blank screen and one question: what name could become the umbrella for all our apps and digital projects? We wanted something elegant, calm, and purposeful. Not just something that sounded good, but a name with enough meaning to guide every creative decision we'd ever make — from interface design to the features we chose to build.

01 — Inspiration That Came from Nature

The inspiration came from an unexpected place: flamingos.

Watching them stand perfectly still at the water's edge, move swiftly when hunting, yet always look graceful and composed — there's a deep balance between stillness, focus, and agility. Flamingos look simple, but they're full of principle.

A question stirred: How do we build a brand that carries those same qualities — stable, adaptive, yet still elegant?

02 — From Flamingo to Flago

Our first instinct was to use the word "Flamingo" directly. But it felt too generic, already overused, and a little cliché. So Flago emerged — a shorter, lighter version that still carried the essence of the flamingo's spirit.

But Flago alone still felt incomplete. We wanted to emphasize the core, the essence, and the philosophy that shapes everything we build. We weren't just building apps — we wanted to build something with a soul. That's when DNA entered the picture.

FlagoDNA was born.

How to Pronounce It

FlagoDNA is pronounced: "Fla-go Dee-En-Ay"

Flago → derived from flamingo, short and lightweight
DNA → a symbol of the core essence and values that guide every piece of work

03 — The Philosophy Behind the Name

FlagoDNA is more than a name. It's a reflection of the principles we stand by:

🎯 Focus
Like a flamingo — precise and deliberate. Every product we build has a clear purpose. No feature exists just to exist.

🔄 Adaptive
Able to move with changing technology, evolving user needs, and the realities of lean development. The world moves fast; brands that last are the ones that move with it.

✨ Elegant & Simple
Clean, light, and refined in every dimension of design and user experience. Simplicity isn't a limitation — it's an intentional choice.

🧬 Core / DNA
A metaphor for the values and philosophy that inform every decision: what gets built, how it looks, and what kind of impact it's meant to create.

04 — The Journey Behind the Name

Finding this name wasn't a clean whiteboard brainstorm. There was uncertainty, frustration, and doubt. We explored dozens of variations, played with countless words, discarded candidate after candidate — until that "aha" moment when DNA clicked into place alongside Flago.

What followed wasn't just relief. It was a kind of quiet certainty — like we hadn't invented the name so much as discovered it. Something that had been there all along, waiting.

05 — What FlagoDNA Has Become

Over time, FlagoDNA grew. What started as just a brand name is now the umbrella for everything we create:

HadisKu — a complete hadith application from 14 Imams, making Islamic literature accessible, offline, and searchable for everyone
FastiQuran — a calm, clean, ad-free Quran reading experience with trusted Indonesian translations
Lens Browser — a lightweight, privacy-focused Android browser with built-in ad blocking and anti-fingerprinting
Sheeply — a collection of peaceful mini-games designed to help you relax, unwind, and find calm in your day
And various other digital experiments along the way

No matter the project, the philosophical compass stays the same.

A Note for Fellow Builders

Having a clear brand philosophy is an underrated asset — especially for small, focused teams. It helps set priorities, say no to irrelevant features, and stay grounded when everything feels overwhelming.

If there's one insight we'd leave you with:

Choosing a brand name isn't just about being "unique" or "catchy." A strong name has philosophical depth, emotional resonance, and alignment with your core values.

FlagoDNA is the DNA of what we value, the inspiration we drew from nature, and a reflection of a journey that's still very much in progress.

FlagoDNA isn't just a name. It's a philosophy, a journey, and the foundation of our work — the DNA of what we believe in and want to share with the world.

Tags: Brand Story Company Philosophy FlagoDNA App Development

HadisKu Is Now Ad-Free: Why I Removed Ads From My Islamic App

Cahyanudien Aziz Saputra — Wed, 01 Apr 2026 13:17:31 +0000

Starting with version 3.0.0, HadisKu is now completely ad-free.

I also removed:

In-app purchases (IAP)
Subscriptions
Unnecessary tracking / analytics

For some people, this may sound like a small update.

But for me, it was a very important decision.

Because honestly, this was never just about removing ads.

It was about bringing HadisKu back to its original intention.

What is HadisKu?

HadisKu is an Islamic app I built to help Muslims read, search, and study hadith more comfortably.

It brings together collections from 14 major hadith sources in one place, with a focus on simplicity, accessibility, and a clean reading experience.

From the beginning, I wanted HadisKu to feel:

calm
lightweight
useful
respectful
focused on learning

Not like a content app that tries to maximize attention.

Not like a product that keeps asking for money every few steps.

Just a simple place to read and learn.

Why removing ads mattered

Ads are common in mobile apps.

And I understand why.

For many indie developers, ads are often the easiest way to support development. Sometimes they are necessary. Sometimes they are the only practical option.

But HadisKu is not just another utility app.

This is an app people open to read hadith.

To reflect.

To learn quietly.

To search for knowledge.

And over time, I started to feel that ads created friction in a place that should feel calm.

Even if the ads were “normal,” they still changed the feeling of the app.

They made the experience less focused.

Less peaceful.

Less aligned with why I built HadisKu in the first place.

So eventually, I had to ask myself a simple question:

If this app is meant to help people learn hadith, why should that experience be interrupted?

That question stayed with me for a long time.

This is bigger than a product update

Removing ads sounds like a technical change.

But for me, it was also a values decision.

With HadisKu 3.0.0, I wanted to make the app feel more honest.

More intentional.

More aligned with the purpose of the project.

That’s why I removed not only ads, but also:

in-app purchases
subscriptions
anything unnecessary that adds friction

I wanted HadisKu to become simpler again.

Not just in UI.

But in spirit.

I want it to be an app that feels comfortable to open without distractions.

An app that respects the user’s attention.

An app that doesn’t constantly try to monetize every interaction.

An app that feels better suited for learning religious knowledge.

HadisKu 3.0.0 is also a meaningful update

This release is not only about removing monetization.

Version 3.0.0 also includes several improvements that came directly from user feedback:

A refreshed app icon
Arabic text search
Hadith detail order settings
- Arabic → Indonesian
- Indonesian → Arabic
Arabic text alignment settings
- Left
- Right
- Justify

A few of these updates were inspired by suggestions from users who took the time to share thoughtful feedback.

That kind of support matters more than many people realize.

For an indie project, sometimes one message, one suggestion, or one kind review can shape the direction of an entire release.

And I’m genuinely grateful for that.

Building small apps teaches you strange things

One thing I keep learning as an indie developer is this:

Sometimes the best product decision is not adding more.

Sometimes it’s removing things.

Removing clutter.

Removing noise.

Removing monetization that no longer feels right.

Removing systems that slowly pull the project away from its purpose.

As developers, we often talk about features, growth, retention, and optimization.

But sometimes the real question is much simpler:

Does this still feel true to what I wanted to build?

For HadisKu, version 3.0.0 is my attempt to answer that question honestly.

I still want HadisKu to keep growing

Removing ads doesn’t mean I want the project to stop growing.

Actually, I want the opposite.

I want HadisKu to become more useful, more refined, and more beneficial over time.

There is still a lot I want to improve.

There are still features I want to build.

There are still platforms I want to support better.

But I want that growth to happen in a way that feels healthier for the product and more respectful to the people who use it.

For now, that means choosing a cleaner direction.

A quieter direction.

A more intentional direction.

If you use HadisKu, thank you

If you have ever downloaded HadisKu, used it, shared it, reviewed it, or sent feedback — thank you.

Projects like this are never built by one person alone, even if one person writes most of the code.

Every suggestion matters.

Every bug report matters.

Every kind word matters.

And sometimes, every honest discomfort matters too.

HadisKu 3.0.0 exists because of that.

Read the original story

If you want to read the original story behind this update, I wrote a longer version on my personal blog:

Original post:
HadisKu kini tanpa iklan

Try HadisKu

If you want to try the app:

Google Play:
HadisKu on Google Play

Final thought

HadisKu 3.0.0 is not the biggest app update in the world.

But for me, it might be one of the most honest ones.

Sometimes progress looks like adding features.

And sometimes progress looks like removing the things that no longer belong.

For HadisKu, this was one of those moments.

We Built 15+ Privacy-First Islamic Apps — Here's Why

Cahyanudien Aziz Saputra — Mon, 30 Mar 2026 14:13:19 +0000

It started with a simple request. Our founder's mom needed a clean, ad-free Hijri calendar widget. He built one for her.

That single app revealed something much bigger — millions of Muslims were relying on digital tools that exploited their faith for profit.

Then in 2020, a popular Islamic app was caught selling user data to military contractors.

That was the moment FlagoDna was born.

The Problem

The world's 2 billion Muslims often rely on apps built with secular, profit-first priorities:

Maximize screen time
Collect and sell user data
Serve targeted ads
Gamify sacred practices

This creates a painful conflict — seeking spiritual resources but getting monetized instead.

What We Built

FlagoDna is a parallel digital infrastructure rooted in Islamic values.

Our architecture principles:

Offline-first — sensitive data never leaves your device
Zero data selling — ever
No tracking — no ads, no behavioral analytics
Honest monetization — freemium + donations, not exploitation

Our Apps

HadisKu — Complete hadith reader from 14 imams, fully offline
FastiQuran — Quran reader with official Indonesian translation, zero ads, zero data collection
AmalanKu — Daily good deeds tracker, designed for self-reflection, not gamified engagement
Lens Browser — Privacy-focused Android browser with built-in ad and tracker blocking

Traction (Fully Bootstrapped)

60,000+  total downloads
 7,500+  monthly active users
    15+  maintained applications
   100%  organic growth (zero paid ads)

No investors. No external pressure. Just building tools the ummah actually trusts.

What's Next

Muslim Launcher — privacy-first Android launcher ($2.99/month)
Muslim VPN — encrypted browsing for Muslim users ($4.99/month)
AI-powered features — without compromising on privacy

We just got featured on Tech in Asia as part of their Startup Spotlight series 🎉

Read the full story → https://www.techinasia.com/building-parallel-digital-world-islamic-values

Tags:
privacy, #islamictech, #android #buildinpublic #bootstrapped #startup #mobiledev #opensource

New Logo, Zero Ads: Meet FastiQuran — The Free Quran App Built for Focus

Cahyanudien Aziz Saputra — Mon, 30 Mar 2026 13:54:01 +0000

The app just got a brand new logo — and if you haven't tried FastiQuran yet, here's why you should.

✨ We Have a New Logo!

FastiQuran just received a refreshed app logo — cleaner, more modern, and designed to better reflect what this app truly stands for: a calm, purposeful, and spiritual space for the Quran.

It's not just a visual update. It's a signal of where FastiQuran is heading — a more polished, more intentional experience for every Muslim who picks it up.

Small change on the surface. Big commitment underneath.

So… What Is FastiQuran?

FastiQuran is a free Quran application built for one purpose: to give you the most peaceful, distraction-free Quran reading experience possible — on any device you own.

No ads. No subscriptions. No pop-ups. No hidden costs. Just the Quran.

We live in an age where even sacred moments get interrupted by notifications and banners. FastiQuran was built as a direct response to that. When you open this app, nothing competes for your attention except the words of Allah SWT.

It's fast. It's lightweight. And it works across Windows, Linux, and Android — with macOS & iOS on the way.

🕌 The Core Experience

FastiQuran isn't trying to be everything. It's trying to be the best at one thing: helping you connect with the Quran, deeply and consistently.

Pure, Ad-Free Reading
Open the app and you're immediately in the Quran. No onboarding walls, no upgrade prompts, no ads mid-scroll. Just clean, beautiful text.

Fast & Lightweight
The app is built to be responsive on any device — even older hardware. Features don't come at the cost of speed.

Cross-Platform Sync
Start reading on your desktop, pick it up on Android, and your bookmarks, progress, and settings follow you everywhere.

📖 Features Built for Real Quran Practice

🔖 Smart Bookmarks

Save any verse or section and return to it instantly. Your reading position is never lost.

🔍 Advanced Search

Search in Arabic, transliteration, or any supported translation. Find any surah, verse, or keyword in seconds.

🧠 Hifz (Memorization) Tools

A dedicated space for those memorizing the Quran — with progress tracking, revision scheduling, and reinforcement tools built in.

📚 Tafsir & Word-by-Word Translation

Go deeper than surface reading. Understand the meaning behind every word with integrated Tafsir and word-by-word breakdowns. (Tajwid support coming in a future update!)

🔊 Audio Recitation

Listen to beautiful recitations of the Quran anytime, anywhere.

📿 Daily Prayers & Dhikr

Authentic daily adhkar and prayers — right inside the app, ready for your daily routine.

🎨 Themes & Custom Fonts

Choose from beautiful themes and comfortable reading fonts to make the experience truly yours.

🆕 What's New in This Update

1. New App Logo
A fresh, modern redesign that better represents FastiQuran's identity — clean, spiritual, and refined.

2. Text Alignment Settings
You can now control how Quran text and translations are displayed on screen. Choose between Left, Right, Center, or Justify — whatever feels most natural for your reading style. A small setting that makes a noticeable difference, especially for those who read in RTL languages.

🌍 Our Mission

FastiQuran exists to serve the global Muslim community — sincerely and without compromise.

✅ A distraction-free space to connect with the Quran
✅ Tools to build meaningful daily reading habits
✅ Advanced features through a simple, accessible interface
✅ Free — for every Muslim, everywhere, always

💬 Try It & Share Your Thoughts

FastiQuran is available now on Android and Desktop.

📱 Google Play: Download on Play Store
🌐 Website: fastiquran.app
Originally published at fastiquran.app

Your feedback shapes every update. If you have suggestions, feature requests, or bug reports — we genuinely want to hear from you.

Built with ❤️ for the Muslim Ummah.

"And We have certainly made the Quran easy for remembrance, so is there any who will remember?"
— Quran 54:17

The Stairs Nobody Talks About

Cahyanudien Aziz Saputra — Sun, 29 Mar 2026 06:33:19 +0000

A note from a solo indie developer who has 15+ apps, 60K+ downloads — and still gets tired.

There's a version of the indie developer story that gets told a lot.

The grind. The launch. The growth chart going up. The "I built this alone" badge worn like armor.

That's not what this is.

I see the path. I know the goal. I've been walking toward it since 2020 — building apps for Muslim daily life, one at a time, solo. Quran apps. Hadith apps. A VPN. A launcher. A vision of a parallel digital ecosystem built on Islamic principles, not Silicon Valley ones.

The destination is clear.

But between where I stand and where I'm going, there are stairs.

And some stairs — you just sit down on.

Not because you failed. Not because you lost users. Not because the product broke or the dream died.

Just because you're tired.

Tired of writing code in silence. Tired of making decisions that nobody else will ever know you made. Tired of being the designer, the developer, the tester, the support team, the marketer, the strategist — all before lunch.

I'm not asking for empathy. I'm not asking for help.

I'm just saying: this is also what it looks like.

In other fields, this feeling has names. The artist who disappears mid-project. The writer who can't open the doc. The founder who stares at the pitch deck and feels nothing.

We don't talk about it much in tech. Because we're supposed to ship. Because "build in public" means showing the wins, not the Wednesday afternoon when you just... couldn't.

But indie developers — whether you're making apps, games, tools, whatever — we live this.

You're not part of a team that carries you when you're slow. There's no standup where someone notices you've been quiet. There's no colleague who brings you coffee and asks if you're okay.

It's just you, the editor, and the silence.

And sometimes the silence gets heavy.

I've shipped 15+ apps. 60K+ downloads. 7.5K people using what I built. I'm incorporated now. I have a pitch deck. I have a roadmap.

And sometimes I still sit on a stair and just... breathe.

Not giving up. Not done. Not even sad, exactly.

Just tired in that specific way that only comes from carrying something alone for a long time.

If you're an indie dev reading this — app, game, plugin, whatever — maybe you know this stair.

Maybe you're sitting on it right now.

I'm not going to tell you to push through. I'm not going to tell you it gets easier or that the launch will fix it.

I'll just say: I see you. The stair is real. And you built real things to get here.

That counts.

Cahyanudien Aziz — building FlagoDNA, one stair at a time.
flagodna.com

Who We Are — FlagoDNA

Cahyanudien Aziz Saputra — Fri, 27 Mar 2026 15:34:28 +0000

We are FlagoDNA.

Not a "Muslim version" of Google.
Not another Islamic app studio.
A developer lab building parallel digital infrastructure for the Ummah.

It started in 2020.

One developer. One mission.
Build tools that actually serve Muslim daily life.

Quran readers. Hadith collections. Prayer trackers.
One app at a time.

Then something happened.

60,000 downloads.
7,500 active users.
15+ apps shipped.

And one uncomfortable truth became clear:

A single app is not enough.

Our phones are not just tools anymore.
They are environments.
They shape attention. Habit. Character.

And right now, those environments are built
by people who do not share our values.

We decided to change that.

FlagoDNA is now building the foundation:

→ Muslim Launcher — a faith-first home screen
→ Muslim VPN — data sovereignty for the Ummah
→ Muslim AI — intelligence grounded in Islamic sources

Not add-ons.
Not plugins.
A foundation.

We build with four values:

Innovation. Push the boundary of what faith-tech can be.
Quality. Privacy-first. Performance-first. Always.
Collaboration. Open source where it matters.
Mlampah Ing Tresno. Walk with love. ❤️

This is our first post as FlagoDNA on DEV.

More coming — behind the builds, the decisions, the stack, the failures.

If you are a builder who cares about what technology does to people,
you are in the right place.

→ flagodna.com

Skedoff Is Now on Google Play: I Built a Quieter Way to Plan Content Offline

Cahyanudien Aziz Saputra — Fri, 27 Mar 2026 13:49:47 +0000

I just released Skedoff on Google Play.

It is a small app, but it carries a very specific idea that I care about a lot:

plan social media content offline, keep your drafts private, and publish only when you're ready.

No cloud dependency.

No forced account.

No subscription.

No risky automation pretending to make your workflow better while quietly taking ownership away from you.

Just your drafts, on your device, waiting for the right moment.

Why I Built It

A lot of social media tools assume the same thing:

you should create an account first
your content should live in someone else’s cloud
your workflow should be wrapped in a subscription
“productivity” should mean automation

I wanted the opposite.

I did not want a louder scheduler.

I wanted a quieter workspace before posting.

Something simple.

Something local-first.

Something that respected the fact that not every creator wants to automate their voice.

That became Skedoff.

It is not really a “social media scheduler” in the usual sense.

It is more like a boundary layer between the idea and the publish button.

What Skedoff Actually Does

Skedoff is a privacy-first, offline-first content planner for:

creators
freelancers
solo builders
small businesses
personal brands
anyone who prefers manual posting with full control

The workflow is intentionally minimal:

Draft → capture ideas anytime
Queue → organize content that is nearly ready
Published → keep a local record of what already went out

That’s the whole system.

No dashboard overload.

No “growth engine.”

No auto-posting pipeline.

The Most Important Design Decision: No Auto-Posting

This is one of the most intentional choices in the product:

Skedoff does not auto-post.

That is not a missing feature.

That is the feature.

You write the draft in Skedoff.

Then when you are ready, you manually open the platform, copy, paste, review, and publish.

For some people, that sounds like extra friction.

For the kind of user I built this for, it is actually creative ownership.

That last manual step matters.

It creates a pause.

And sometimes the pause is the product.

What It Avoids (On Purpose)

Skedoff intentionally avoids a lot of the things that modern productivity apps normalize:

No account creation
No cloud sync
No monthly subscription
No social account connection
No analytics
No tracking
No developer-controlled draft storage

I wanted it to feel smaller.

And more honest.

I think a lot of software would be better if it stopped trying to become your entire workflow.

What’s in v1

The first public release focuses on the essentials:

Offline-first social media post planning
Local draft storage on device
Draft → Queue → Published workflow
Platform tagging for multiple social platforms
Search and filtering
Clean writing experience
Local publication history

It is built for people posting manually to platforms like:

Instagram
X / Twitter
LinkedIn
Threads
TikTok
Facebook
Bluesky
YouTube

Not to replace those platforms.

Just to give you a better place before them.

Why This Matters to Me

This app is small.

But small does not mean unimportant.

Skedoff represents a kind of software I want to keep building:

tools that respect boundaries
apps that work without the internet
products that do less, but do it with intention
software that doesn’t force accounts for basic utility
interfaces that help you think before you react

A lot of apps want to help you post more.

Skedoff is for people who want to post more intentionally.

Available Now

If this sounds like your kind of tool, Skedoff is now live on Google Play:

👉 Google Play: Skedoff: Offline Post Planner

I also wrote a fuller launch post on my blog if you want the more complete version:

👉 Full release post: Skedoff Is Now on Google Play: A Quieter Way to Plan Content Offline

And the project page is here:

👉 Project site: Skedoff Official Page

Final Thought

I used to think I was building a scheduler.

What I was really building was a boundary.

That idea still defines the product.

Plan offline. Post when ready.

If you try it, I’d genuinely appreciate honest feedback.

Building AmalanKu: Why I Made a Privacy-First, Offline-First Muslim Companion App

Cahyanudien Aziz Saputra — Thu, 26 Mar 2026 12:59:29 +0000

When I started building AmalanKu, I thought I was making a simple Muslim companion app.

But the more I worked on it, the clearer it became: I wasn’t just building another religious utility.

I was trying to build a different kind of digital space.

A quieter one.

One that feels personal, respectful, and less invasive than what modern apps often normalize.

The problem with many “helpful” apps

A lot of apps are built around the same default assumptions:

maximize engagement
collect behavioral data
add accounts, sync, and analytics by default
measure everything possible

That model works for many product categories.

But I think it creates the wrong atmosphere for spiritual tools.

Some things shouldn’t feel like dashboards.

Some things shouldn’t feel gamified.

Some things shouldn’t feel like they’re being optimized for retention loops.

That discomfort is what led me to build AmalanKu.

What I wanted the app to feel like

Before thinking about features, I kept asking myself:

What should a spiritual app feel like?

Not “powerful.”

Not “sticky.”

Not “social.”

For me, it should feel:

calm
lightweight
respectful
useful without becoming intrusive
private by default

That shaped the product more than any roadmap ever could.

Privacy is more than a technical feature

When developers hear “privacy-first,” we usually think of technical checklists:

no trackers
no analytics
no unnecessary permissions
no third-party SDKs

Those things matter.

But with AmalanKu, privacy is also philosophical.

Some forms of digital activity are deeply personal. Not just “sensitive” in a compliance sense, but personal in a way that belongs to someone’s inner life, discipline, and relationship with faith.

That’s why I wanted the app to be built around digital restraint.

Not just secure by design.

Also quiet by design.

Why I chose offline-first

An offline-first product changes the default relationship between the app and the user.

It means:

the app still works without a server
core usage doesn’t depend on cloud infrastructure
data stays with the user by default
trust isn’t constantly outsourced to a backend

That’s not just a technical decision.

It’s a product values decision.

For this kind of app, offline-first felt natural because it should feel like a personal companion, not a service that continuously asks for trust.

Designing against noise

A lot of apps become noisier over time:

more prompts
more banners
more nudges
more engagement hooks
more reasons to come back for the app itself

But I didn’t want AmalanKu to become the center of attention.

I wanted it to support the user, then get out of the way.

That changes a surprising number of product decisions:

which features you reject
which metrics you don’t collect
which UX patterns you avoid
which monetization patterns you refuse to build around

Sometimes product design is not just what you add.

Sometimes it’s what you intentionally leave out.

A broader lesson

Building AmalanKu reinforced something I keep returning to:

Not every digital tool should be loud, connected, measurable, and extractive.

There’s still room for software that is:

local-first or offline-first
private by default
intentionally limited
easier to trust
designed to serve the user, not the platform

That’s the kind of software I want to keep building.

Final thought

I didn’t build AmalanKu to compete on feature volume.

I built it because I believe some tools should protect stillness instead of interrupting it.

If a spiritual app can help someone reflect, remember, or stay consistent—without surveillance, pressure, or noise—that already feels meaningful.

If you want the full story and the longer product philosophy version, I wrote the full post here:

👉 Building AmalanKu: Why I Believe Spiritual Tools Should Feel Quiet, Personal, and Private

And here’s the companion video:

🎥 Watch AmalanKu on YouTube

Building Skedoff: Why I Made an Offline-First Social Media Planner Instead of Another SaaS Scheduler

Cahyanudien Aziz Saputra — Wed, 25 Mar 2026 10:33:45 +0000

When I started building Skedoff, I thought I was making a lightweight social media scheduler.

Turns out, I was actually building something much narrower — and much more intentional.

Not another SaaS dashboard.

Not another auto-posting tool.

Not another “connect all your accounts” platform.

What I really wanted was a local-first boundary between writing and publishing.

That difference ended up shaping the entire product.

The problem I had with existing schedulers

Most social media scheduling tools assume the same workflow:

create an account
connect your social platforms
store drafts in the cloud
pay monthly
automate publishing

That model makes sense for:

agencies
marketing teams
content operations
people managing multiple clients

But I’m not building for that first.

I wanted something for:

solo creators
indie builders
freelancers
small businesses
people who still want manual control

I didn’t want unfinished drafts sitting on someone else’s server.

And I didn’t want “productivity” to automatically mean “automation.”

What Skedoff actually is

Skedoff is a privacy-first, offline-first social media content planner.

It does not:

require an account
sync to a backend
connect to social APIs
auto-post
collect analytics

Instead, it gives you a simple local workflow:

Draft → Queue → Published

That’s it.

You write posts offline.

You tag the intended platform.

You move them through a small workflow.

Then when you’re ready, you manually open the real platform and publish.

This is intentionally less “powerful” than a traditional scheduler.

That’s the point.

Why I intentionally avoided auto-posting

From a product perspective, auto-posting is tempting.

It sounds like the obvious “upgrade.”

But it comes with tradeoffs:

platform integrations
auth complexity
token storage
backend requirements
API policy changes
reliability issues
more user trust required
more surface area for bugs

And more importantly, it changes the product philosophy.

The moment the tool becomes responsible for publishing, it stops being a planning space and starts becoming infrastructure.

I didn’t want that.

I wanted the app to stay focused on:

preparation
intentionality
low friction
privacy
control

For this product, manual posting is not a missing feature.

It’s a design choice.

Offline-first wasn’t just a technical choice

“Offline-first” is often described as an implementation detail.

In Skedoff, it’s also a product stance.

I wanted the app to feel like it belongs to the device, not to a service.

That means:

it works without internet
the core experience is always available
no server dependency
no “sign in to continue”
drafts stay local by default

That’s especially important for content planning.

Publishing is online.

Planning doesn’t always need to be.

Current architecture choices

Skedoff is intentionally simple right now.

The current direction is:

Flutter for cross-platform development
local-first storage instead of cloud sync
three-tab workflow for Draft / Queue / Published
platform tagging without external integrations
minimal navigation complexity
manual publish flow instead of API-based automation

A lot of the challenge here isn’t adding more code.

It’s resisting code that pushes the app away from its core promise.

Why the UX is deliberately small

A lot of productivity tools become noisy because they try to solve every adjacent problem.

I wanted Skedoff to avoid that.

So instead of a big navigation structure, I kept it intentionally narrow:

Draft → ideas and raw captions
Queue → content you’ve decided is ready soon
Published → a local record of what went out

That’s enough structure to be useful, but not enough complexity to become another management system.

The more I built it, the more I realized:

I wasn’t building a scheduler.

I was building a pause button.

Current status: submitted to Google Play

Right now, Skedoff is in the most awkward indie stage:

technically done, emotionally not fully convinced.

Current status:

UI done
local database done
core workflow working
platform tagging working
search/filtering working
Android build prepared

And the app is now submitted to Google Play for review.

If everything goes smoothly, I’m expecting roughly 3–5 days before it goes live, which seems normal for a first release (assuming review goes smoothly).

That phase is always weird.

There’s a gap between:

“the app works”
and
“I’m ready to let strangers use it”

I’m in that gap right now.

What comes next

I’m trying to keep v1 intentionally narrow.

Next things I’m considering:

local notification reminders for queued posts
bulk actions
export / backup improvements
small workflow refinements
possibly optional, privacy-respecting crash reporting later

The hard part isn’t deciding what to add.

The hard part is deciding what not to add.

Because I don’t want Skedoff to slowly become the exact kind of tool I originally didn’t want to use.

Product page and original write-up

If you want the full founder/story version, I published the original article on my blog:

Original post: Building Skedoff: I Thought I Was Making a Scheduler, but I Was Really Building a Boundary

And the product page is here:

Skedoff: https://flagodna-developer.github.io/skedoff/

I’m Cahyanudien Aziz Saputra, building under FlagoDNA.

If you’ve built something similar — or intentionally avoided “obvious” features to protect a product’s philosophy — I’d love to hear how you handled that tradeoff.

At Night, the Downloads Don’t Talk Back

Cahyanudien Aziz Saputra — Mon, 23 Mar 2026 06:57:11 +0000

I’ve built more than 15 apps.

Mobile apps. PC apps. Small tools. Utility projects. Quiet things.

Most of them were not requested.

No one came to me and said, “Please build this.”

I just saw problems.
Small friction.
Missing tools.
Bad UX.
Things that could be simpler, cleaner, more useful.

And every time I thought the same thing:

This should exist.
This could help someone.

So I built it.

Over time, all those apps reached around 60,000 downloads, with around 8,000 monthly active users across them.

On paper, that sounds decent.

Not huge. Not viral. Not some startup success story.

But real.

Real people have used things I made.

If you want the home version of this essay, I also published it on my personal blog: At Night, the Downloads Don’t Talk Back.

And still, there’s something I almost never hear people talk about:

You can build for thousands of people and still feel completely alone at the end of the night.

That’s the strange contradiction of being a solo builder.

On one side, you’re making things for people.

On the other side, when the screen is still glowing at 2AM, the room is quiet, the code is half-finished, and your brain is exhausted, you can still feel like nobody really sees you.

People see the outside.

They see:

the late nights
the PC
the phone
the same desk
the same room
the same routine

Sometimes I think they assume the simplest version:

no life
always online
isolated
weird sleep schedule
another lonely person who spends too much time in front of screens

What they don’t see is the invisible part.

They don’t see:

the bug that stole four hours
the feature rewritten three times
the UI flow changed again because the first version felt wrong
the tiny improvements no one notices
the release notes nobody reads
the silent belief that maybe this small thing will make someone’s day easier

They don’t see the emotional weight of building something useful in silence.

That part is hard to explain.

Because I don’t build only for myself.

Yes, I like building.
Yes, I like solving things.
Yes, there’s something satisfying about turning an idea into a real tool.

But there’s another layer too.

I build because I believe some of these things matter before the world can prove it.

Sometimes I can see a future shape of what I’m making.

Not perfectly.
Not like magic.
Not with certainty.

Just enough to feel the direction.

Enough to believe that what looks small today might become meaningful later.

Enough to believe that if I keep building, keep refining, keep releasing, something will compound.

That’s the weird life of a solo builder.

You are often walking on weak evidence.

The present doesn’t fully confirm you.

The metrics are not where you want them.
The adoption is slower than your vision.
The people around you don’t really understand what you’re doing.
And the gap between what you see internally and what exists externally can feel brutal.

But still, you keep walking.

Because somewhere far ahead, even in the dark, you can see a little light.

I think a lot of builders live there.

In that space between:

current reality
future possibility

That space can be powerful.

It can also be lonely.

And the loneliest part isn’t always failure.

Sometimes the loneliest part is success that doesn’t feel like it counts emotionally.

People use your app.
The numbers go up.
Downloads happen.
Active users are there.

But then the night comes.

And the truth is:

downloads are numbers.
Analytics are cold.
Stats don’t talk back.

A graph can tell you people came.

It cannot tell you:

“I saw what this cost you.”
“This helped me.”
“This mattered.”
“Thanks for building this.”

That’s the part I think people misunderstand.

A lot of builders are not asking for fame.

Not applause.
Not a huge audience.
Not some dramatic recognition.

Sometimes we only need one or two real people to say:

“Thanks for building this.”

That’s enough.

Not for ego.

For fuel.

Because a simple thank you does something analytics never can.

It means:

the work reached someone
the time wasn’t wasted
the frustration had a purpose
the invisible hours became real
you were not building into a void

And maybe that’s the hidden emotional truth behind a lot of useful software:

You can help many people
and still quietly starve for a little human recognition.

Not because you’re weak.

Not because you need attention.

Because you’re human.

If you’re a solo builder, indie dev, designer, or someone who keeps making things in silence, maybe you know exactly what I mean.

Maybe you’ve shipped things that solved real problems.

Maybe people use what you made, but the people around you still only see “screen time.”

Maybe you’ve stayed up late fixing something no one will ever notice.

Maybe you’ve improved a tool because you knew it could be better, even if nobody asked.

Maybe you’ve sat in the dark after a long session and asked yourself:

Why am I doing this?

And maybe the answer is complicated.

Maybe part of it is obsession.
Maybe part of it is purpose.
Maybe part of it is identity.
Maybe part of it is hope.
Maybe part of it is the quiet belief that one day the future will catch up to the work.

I don’t know if everyone understands that kind of life.

Maybe they never will.

But I know this:

A simple thank you can carry someone farther than you think.

So if someone built something that made your day easier, saved your time, reduced your friction, or quietly solved a problem for you, tell them.

Leave the review.
Send the message.
Write the comment.

You might think it’s small.

It’s not.

For some of us, that one sentence becomes heart fuel.

It becomes enough to keep going one more week.
One more update.
One more release.
One more version.
One more long night.

And whether anyone says it or not, I’ll probably still keep building.

Quietly.

Somewhere in the underground where most people never look.

Still alive.
Still making things.
Still walking the long road.

Because this is not just something I do.

This is my life.

Building Skedoff: Why I’m Making an Offline-First Content Planner

Cahyanudien Aziz Saputra — Tue, 17 Mar 2026 10:56:37 +0000

Yesterday, I talked about why I stopped trusting most scheduling tools.

Today, I want to talk about what I’m building instead.

It’s called Skedoff.

A small app with a simple idea:

Plan content offline. Post when ready.

Not auto-post.

Not cloud-first.

Not another dashboard asking you to connect all your social accounts.

Just a quieter layer between writing and publishing.

Why I Started Building It

Most social media schedulers assume the same workflow:

create an account
connect your platforms
trust a third party with your drafts
automate as much as possible
pay monthly

That model makes sense for teams and marketing pipelines.

But it never fully worked for me.

Sometimes I don’t want “publish later.”

Sometimes I want:

write offline
decide the platform
set a reminder
come back when the moment feels right
copy, paste, publish intentionally

That difference matters more than I expected.

So instead of trying to automate posting, I started building something else.

What Skedoff Actually Is

At first, I thought I was building a lightweight scheduler.

But the more I worked on it, the less it felt like one.

Skedoff is starting to feel more like this:

a private staging space for words that aren’t ready yet

That became the real product idea.

Not a social media control center.

Not a SaaS dashboard.

Not a growth tool.

Just a privacy-first, offline-first content planner for people who want more ownership before they publish.

Current Build Status

Right now:

UI is done
database is done
core flow already works

The app is being built with Flutter, and the goal is to keep the experience consistent across:

Android
iOS
Windows
macOS
Linux

The core flow is intentionally simple:

Write offline
Tag the platform
Set a reminder
When ready: copy, paste, publish

No account.

No cloud.

No subscription.

Your drafts stay on your device until you decide they are ready.

Why It’s Not Released Yet

Even though the app already works, I’m not releasing it yet.

Because now I’m in the part that matters most:

polishing the UX
refining the writing flow
improving the small details
making the app feel calm, deliberate, and reliable

Technically “done” is not the same as ready.

And for a tool built around trust and ownership, the details matter.

A lot.

Why the Name Is Skedoff

The name comes from:

schedule
offline

But the “off” matters for more than just offline mode.

It also feels like:

off the cloud
off the pressure
off the feed
off the urgency to publish immediately

That felt right for the product.

Because this app is less about automation…

…and more about intentional publishing.

Full Write-Up

I wrote a fuller version on my own blog, where I go deeper into:

the product philosophy
why I chose offline-first
what I learned while building it
why it no longer feels like “just a scheduler”

👉 Read the full post here:

Building Skedoff: A Quieter Way to Plan Content Offline

Still building.
Cahyanudien Aziz Saputra