The slogan answer is easy: review every day. The real answer is more nuanced.

Daily review is usually ideal, but not every missed day means failure, and not every daily streak means the system is healthy. What matters more is the pattern your review history reveals over time.

Since reviews happen in Anki, that history lives in Anki's Stats: retention, intervals, due counts, and the calendar heatmap. It turns a vague feeling into a pattern. Are you reviewing consistently but grading too generously? Are you skipping, then overloading? Are you only touching easy material? Daily Portion keeps its own simpler record — whether you finished today's reading.

Those questions matter more than the slogan alone.

Quran parts in Quran Life are not just labels. They define your current territory.

When you choose an active part, the app uses that decision to focus your daily portion and its statistics. Reviews, on the other hand, are global in Anki — changing the active part never hides, suspends, or reschedules your Anki cards. If you want a Surah out of reviews while you work elsewhere, suspend it in the Anki Browser.

That split keeps the system simpler in practice: Daily Portion is your scoped daily territory, Anki is the full review memory.

The normal progression is usually to begin with a part you already learned, so you can stabilize your workflow on familiar ground. After that, you move gradually into parts you have not yet learned, one territory at a time, until eventually the whole Quran is learned and you can switch to the all-Quran mode.

So a part is not just an organizational label. It is the answer to a practical question: what section of Quran am I actively trying to keep moving right now, without drowning the rest of the system?

Quran Life's mindmap editor is built on top of tldraw, so it behaves like a real canvas rather than a text field pretending to be visual.

The editor starts from a lasso-style selection workflow, which fits mindmapping better than forcing you into ordinary box-selection first. Freehand drawing is still the preferred method because it usually gives the most natural map, but the editor also accounts for people who do not think or draw well that way. That is why it gives you arrows, text, and normal selection tools too.

So the important thing to understand about the editor is not only that it exists. It is that Quran Life treats it as an actual working environment for mapping, not as a decorative attachment on the side.

There are two instincts with mutashabihat. One is to study everything early so you are never surprised. The other is to wait until confusion appears and then fix only what became a real problem.

Both have truth in them, but neither should be used blindly. There is no automatic timing engine making this decision for you — you set the timing yourself.

Study similarities before they become chaos, but do not flood yourself with distinctions that have no active context yet. A practical split: when a confusion actually happens during review, flag the card red immediately (reactive). Once a week, pick one tagged Surah and deliberately compare its similar verses on the mindmap (proactive).

The best moment is usually just before a verse becomes vulnerable, not long before and not long after.

Not every mutashabihat issue deserves the same treatment.

Sometimes a similarity is not a real problem for you, even if it looks similar on paper. In that case, ignoring it is the honest choice. You are not saying the verses are unrelated. You are saying this is not an active confusion point in your memorization — so don't flag it, and don't clutter your map for it.

Other times it is a real problem, and then the goal is not just to label it but to resolve it. That means flagging the card, separating the two verses far apart on the mindmap, and adding the thematic distinction — until the confusion stops recurring. A resolved similarity is one you unflag and remove from your weekly check because it no longer fails.

And then there is one more important category: the similarities only you notice. Different users feel different pulls between verses. One person's mind may keep jumping between two places that another person would never confuse. When that happens to you, flag it and note the pair in your mindmap notes — your personal confusion points deserve the same treatment as the well-known ones.

So it's really about three attitudes together: some similarities should be ignored, some should be worked until resolved, and some need to be added by you because your own mind is showing a connection no list captured.

If similar verses are shown too early, they become noise. If they are shown too late, confusion has already hardened.

So don't try to study every similar-verse pair from day one. A similarity becomes worth your time when it has actually surfaced in your review — you confused the verses, or a card failed — and at least one side of the comparison is learned well enough to make the distinction meaningful.

That is why similar-verse work feels tied to the Surah you are currently reviewing, not to a giant master list. In practice: review failures and red flags surface the relevant pairs, the card's extra context verses let you verify them, and the mindmap separation resolves them. Distinctions appear when they can reduce confusion, not as overhead you study in advance.

Quran Life is not being built as a generic productivity app with Islamic branding. It is trying to become a serious memorization system — and it took its current shape deliberately: an Obsidian plugin for mapping and daily reading, with Anki doing what Anki is best at, scheduling reviews.

For now, the most important milestone is not a flashy new feature. It is trust in the method: does mindmap-first memorization with spaced review actually convince real users once they try it?

If it does, the next priorities are very clear: keep the plugin stable and low-bug, finish the pre-made mindmap collection, and keep improving the documentation until users can really understand the ins and outs of the method and the workflow.

So the roadmap is less about a long feature wishlist and more about one question: can Quran Life stay focused on the core memorization method while the tooling around it keeps getting more reliable?

Many Quran memorization apps help you repeat. Quran Life is trying to help you structure, diagnose, and retain.

That difference matters. Repetition is necessary, but by itself it does not explain why one surah feels stable while another keeps collapsing. Quran Life is built around visual mapping, review timing, mutashabihat handling, and error-aware maintenance.

So the comparison is not really "more features" versus "fewer features." It is a different theory of memorization.

Most apps optimize for tracking activity. Quran Life tries to optimize for building a memory system.

Quran Life is not anti-repetition. It is against relying on repetition alone when structure and distinction are missing.

Traditional rote memorization can push verses into short-term familiarity very quickly. But when the structure of the surah, the transitions, and the mutashabihat are weak, that familiarity can stay fragile.

Quran Life treats repetition as one tool inside a larger system. The map gives place. The review schedule gives timing. The mutashabihat work gives distinction.

So the real contrast is not repetition versus no repetition. It is repetition alone versus repetition supported by structure.

Part mindmaps and surah mindmaps do not compete. They operate at different scales.

A surah map gives local structure. A part map gives large-scale orientation across a wider territory. And above those, Quran Life also uses the meta mindmap layer, which helps you keep track of the broadest structural picture beyond one ordinary part map.

So the relationship is not either-or. It is zoom level. Surah mindmaps help you navigate inside the surah. Part mindmaps help you see how several surahs or sections belong together. The meta mindmap helps you think about the larger frame in which the parts themselves sit.

This matters because students often lose stability not only inside one surah, but also at the boundaries between surahs, parts, and broader structures. Each layer supports the one below it.