ASO Journey — Rewriting Everything from the App Name Down

We rewrote fecit’s entire App Store presence. Title, subtitle, keywords, description — all of it.

Because the existing messaging didn’t communicate what fecit actually is.

The Problem

The old app name was just fecit. The subtitle was “Capture tasks fast, organize deeply, and focus on what gets done.” Not bad, but it sounded like every other to-do app out there.

fecit isn’t just a to-do app. It’s a tool that helps you analyze your current situation, identify the gap to your goal, name your obstacles, and work through them step by step. None of that was in the title.

App Name: What to Communicate

The first idea was “Goal Achievement Planner.” Too heavy. fecit also handles “take evening meds” — not everything is a life goal.

After many iterations:

fecit - Achieve Your Goals

“Achieve” connects naturally with fecit’s Latin meaning (“he/she made it”). It’s aspirational without being overwhelming.

Korean version needed a different tone:

fecit - 목표를 이루는 플래너

“이루다” (to achieve/fulfill) is softer than “달성하다” (to accomplish), and “플래너” (planner) keeps it grounded in daily use.

Subtitle: The 80-Character Challenge

Google Play’s short description has an 80-character limit.

fecit’s core loop is plan → analyze → prepare → execute → reflect. We needed to fit that in one line.

From quick tasks to big goals — plan, analyze, prepare, execute, and reflect.

79 characters. “From quick tasks to big goals” shows the range. The five verbs show the difference from other to-do apps.

Keywords: Filling Every Character

iOS keywords allow 100 characters. Words already in the title and subtitle don’t count, so they get excluded.

todo,task,habit,routine,calendar,reflect,productivity,checklist,project,tracker,focus,daily,streak

93 characters of pure search potential.

Description: Features as Stories

The old description focused on “fast and simple task app.” Not wrong, but it missed everything we’d built since.

The new description highlights:

• Analysis section — Current/Expectation/Obstacle GAP analysis framework
• Guide Mode — Step-by-step guided task creation
• Preparation section — Materials, tools, venues, personnel, qualifications
• Reviews — Satisfaction rating + reflection, daily and weekly reviews
• Projects — Team invites, task assignment

Each paragraph starts with a situation, not a feature:

When a goal feels unclear, turn on the Analysis section.
Write down where you are now (Current), where you want to be (Expectation),
and what stands in the way (Obstacle).

Not “There is an Analysis section” but “When a goal feels unclear” — starting from the user’s problem.

Landing Page Alignment

After changing ASO, the landing page was out of sync.

• Headline: “Let’s get things done!” → “Achieve Your Goals!”
• Steps: Capture/Organize/Finish → Plan/Execute/Reflect
• Solution: “One app, every task” → “One app, every goal”
• Features: Steps → Analysis (Current/Expectation/Obstacle)

Unifying the message across App Store and landing page means fecit can be explained in one sentence:

“A planner that helps you achieve your goals.”

User Reviews

We only had two reviews, but two is better than zero. Real user words beat any marketing copy.

“The features are surprisingly detailed. Depending on how you use it, the possibilities are endless.” — Google Play Review

“Reading the developer’s guides, you can really feel how much thought and care went into building this app.” — App Store Review

Just two lines. But placed right above the download button, they carry weight.

Lessons

1. App name balances search and brand. “fecit” alone doesn’t get found. “Task Manager App” alone doesn’t stand out.

2. Put your differentiator in the subtitle. “plan, analyze, prepare, execute, and reflect” — no other to-do app says all five.

3. Start descriptions with situations, not features. “When a goal feels unclear” lands harder than “There is an Analysis section.”

4. Keep App Store and landing page in sync. Different messages in different places create confusion.

Will this ASO work increase downloads? We don’t know yet. But at least what fecit is — and why you’d use it — is now clear. That’s step one.