Some mutashabihat happen at the transition between verses. The confusion is not only in one phrase, but in the point where one ayah leads into another. Other mutashabihat happen inside the verse itself, where the confusion sits in the internal wording of the ayah.

That difference matters during review. When the mutashabihat sits at the boundary between verses, the card's extra context verses after full reveal help you stay oriented, so you do not get stuck only because you lost your place in the transition. The extra context is trying to help you identify the wording problem without letting verse-boundary confusion become a fake extra obstacle.

Another useful classification is by direction.

Some mutashabihat are one-way. A verse in one surah strongly points your mind toward another surah, but not necessarily back in the same strength. Others are two-way, where both surahs can pull you back and forth into each other.

That directional difference often depends on how you structured the surah mindmaps. If one surah has a much stronger or more explicit structure, it may mostly pull the other one in one direction. If both surahs are structured in a way that creates similar pressure, the mutashabihat starts behaving like a back-and-forth link.

This is another reason mindmap quality matters. Mutashabihat are not only about shared wording. They are also about how clearly each verse lives inside its own structure.

So when you choose where the surah should be split, you are also deciding how that surah will be carried in review.

That is why re-importing treats those edits carefully. When you export again and re-import into Anki, matching groups are updated in place and keep their review progress, while genuinely new groups arrive as New cards.

When you edit only the mindmap, nothing resets — your notes and images update but all dates stay. When you change the splits themselves, the old group card becomes outdated: delete it in the Anki Browser, since re-importing never removes cards by itself.

So the practical idea is simple: the surah mindmap gives the route, the verse groups break that route into reviewable pieces, and re-importing preserves what is still valid while you manually clear what no longer matches.

In practice, that means we do not build them from one source file and call it done. We compare five source files, look at how each one structures the surah, and ask which structure feels the most intuitive while still remaining faithful to the text and its meaning.

Sometimes one source is clearly the strongest. Sometimes two or more structures each get something important right, so we merge them. And sometimes the existing structures are still not intuitive enough for memorization, so we try building another structure ourselves and test whether it fits naturally with one of the existing readings or with the majority of them.

That is why building a pre-made mindmap is both a correctness exercise and a usability exercise. The point is not to replace the student's thought. The point is to give the student a serious starting skeleton that can later be edited, simplified, or expanded based on personal memory.

If you chase correctness in a purely academic way, the map can become too dense or too literal to function as a memory aid. If you chase intuition without discipline, the map can become personally satisfying but structurally misleading.

Part of the beauty of the Quran is that different people, with different styles of thinking, naturally notice different patterns in it. That is not a flaw in mindmapping. It is part of why personal mapping can work so well. The goal is not to erase that difference. The goal is to let the student benefit from personal intuitiveness without violating the actual flow, wording, and meaning of the surah.

So the balance is this: keep the text honest, keep the meaning honest, and then allow yourself to choose the branch structure, labels, and grouping style that makes the surah easier for you to carry. A map is not a tafsir replacement and it is not random art. It is a memory structure that should still respect the shape of the surah.

When the pre-built maps do arrive, the choice will not only be between using one as-is and rebuilding everything from zero. There will be a very useful middle ground: import or start from the pre-built map, then edit it until it feels like yours.

That middle ground is often the strongest option. You save time because you are not starting from a blank canvas, but you still gain ownership because you are adjusting the branches, labels, and transitions according to how you actually understand the surah.

So the better question is not "pre-built or custom?" It is "how much structure do I already have, and how much of it do I still need to personalize?" The important thing is not which option looks more advanced. The important thing is whether the map becomes real in your memory.

Since reviews live in Anki, load statistics live there too: Anki's Stats show your retention, upcoming due counts, and review history. In the plugin, the Daily Portion tab shows how many days your current part will take at your daily minutes target. Together they answer whether your current pattern is building a sustainable rhythm or quietly stacking too much pressure into future days.

The practical value is simple: it helps you judge how much new work you can safely add. If Anki's upcoming due counts are already heavy, that is a sign to be conservative with new exports or new memorization. If the load is stable, you can add more with more confidence.

This matters because hifdh often breaks down gradually, not dramatically. Turning "I feel behind" into visible numbers — due counts in Anki, completion days in Daily Portion — lets you act before the system becomes too heavy.

Eligibility comes first. The app looks at your active part and removes any surah you explicitly unchecked in Surahs in Portion. Daily portion is for familiarization through reading or listening — it is deliberately separate from Anki reviews, which have their own scheduling and are never affected by these checkboxes.

That choice is reversible. Re-check a surah and it rejoins the daily cycle; uncheck it and it leaves daily reading (to hide it from reviews instead, suspend its cards in Anki).

Once the eligible surahs are selected, Quran Life starts from your active part and your daily minutes target, estimates how much content fits that time in your current mode, and then snaps that target to a meaningful stopping point. The cycle length is derived afterward from the remaining eligible material, not forced in advance.

That snapping matters. The app prefers to stop at a surah ending when possible. If that does not fit, it looks for a rub boundary. If that does not fit either, it looks for a ruku boundary. If none of those fall within the target window, it falls back to the nearest ayah boundary.

So the daily portion is based on ruku and other structural logic, not only raw word count. The goal is not just to keep you busy today. The goal is to keep your current territory moving in chunks that feel finishable and repeatable.

This matters because many students either choose too little and drift, or choose too much and quietly stop being consistent. A good daily portion is not the largest amount you can survive for one day. It is the amount you can repeat long enough for the sound and flow of the surah to become familiar.

For many people, something like 2 to 3 cycles is a reasonable point before selective rote shortcuts start becoming useful. But that number is not a law. It depends heavily on the person and on how much prior contact they already had with the surah.

If the surah already feels half-known, rote reinforcement can come earlier. If the surah still feels foreign, even 2 or 3 cycles may not be enough yet. The practical question is not whether rote repetition is allowed. It is when it stops being a shortcut and starts becoming a crutch.

If the cycles have already made the surah familiar, a small amount of rote reinforcement can be efficient. If there is still no structure or familiarity, rote repetition often creates shallow recall.

Listening helps the sound, rhythm, and broad flow settle in more naturally. Reading can make sequence and visual phrasing feel more concrete. But this should not be turned into a theory of fixed learning styles. People mostly have preferences, not sealed-off learning categories.

In many cases, the more senses you engage, the better. Listening with focus while reading can be stronger than either one alone. Reading aloud can also be stronger than silent reading because you are involving voice, sight, and hearing together.

So the practical question is not "what type of learner am I?" The practical question is "what combination helps this surah settle into me more deeply and more consistently right now?"

Quran Life launched at a stage where not all planned part mindmaps were ready yet. In particular, the six other parts still needed their mindmaps. That was known. The launch was still intentional, because waiting for total coverage would have delayed the more important test: does the method actually convince real users once they try it?

That was the main early challenge. Quran Life is not entering a crowded category with many similar tools proving the same method. We are basically alone in this space, which means the first job is not only shipping features. It is persuading people that this memorization technique is effective in the first place.

For that reason, the first-launch message has to be honest. It should explain what is already strong, what is still incomplete, and why the product was launched anyway. Honest launches build more trust than inflated ones.

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.

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?

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.

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.

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.

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.

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?

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.

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.

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.