Vivran v2 packs a lot in. If you just read Meet Vivran v2 and felt a small wave of "where do I even start," this post is for you. Six screens, three timer modes, completion criteria, the Logbook, the Advisor Library, bring-your-own-AI: it is a real workspace now, and a workspace you try to use all at once is a workspace you abandon by Thursday.
So this is the opposite of a feature tour. It is a plan for using almost none of it at first, then adding one thing at a time as it earns its place. And because LairsFlow is not the thing you study from, it is the thing that watches how you study, the second half of this post is about fitting it around what you already do: your online lectures on whatever platform you use, your offline coaching, your self-study, without changing any of it.
The one rule: LairsFlow measures your routine, it does not replace it
Read this before anything else, because it removes most of the pressure.
LairsFlow does not want you to study differently. You keep watching the same lectures, sitting in the same coaching class, solving from the same modules and DPPs. LairsFlow sits alongside that and turns it into honest data: how long you actually focused, how the questions actually went, how far along a chapter actually is. Nothing you already do has to move.
That means there is no "correct" way to onboard and no penalty for using one feature and ignoring the rest for a month. Start with the smallest useful piece and let the rest wait.
Week one: use exactly one screen
For your first week, ignore five of the six screens. Open Home and use the timer. That is the whole assignment.
Pick your default mode based on what you spend the most time doing:
- If most of your day is solving questions (DPPs, modules, PYQs), stay in Practice mode. Set a time budget for one question, attempt it, log what happened: right or wrong, and which chapter. That single habit is the entire foundation of the app.
- If most of your day is lectures or reading, use Stopwatch mode. Start it when you begin, stop it when you break, and just bank the time under the right subject.
Do not set up completion criteria. Do not open the Advisor. Do not log a mock. Just build the reflex of starting the timer when you sit down and stopping it when you get up. Everything else in v2 is only useful once this habit exists, because everything else is computed from it.
By the end of week one you want one thing to be true: starting the timer feels automatic, not like a chore you remember three questions late.
Week two: look at the Dashboard, and log your first mock
Now open the Dashboard. You will have a few days of real data in it. Do not analyse it hard. Just notice two things: where your time actually went by subject, and whether your accuracy is where you assumed it was. Most people are mildly surprised by at least one of the two, and that surprise is the entire point of the app.
This is also the week to open the Logbook once, right after your next mock test, and log it: your per-subject scores, what the test covered, a note or two. You only do this a couple of times a month, so there is no habit to build, just remember to do it the evening of a mock while the numbers are in front of you. If Reading the LairsFlow Dashboard is open in another tab while you do this, even better.
Week three: set completion criteria on two chapters, not twenty
Only now open Subjects and Goals, and resist the urge to configure everything. Pick two chapters: one you genuinely feel solid on, and one you have been avoiding. Set a completion criterion on each (something like "50 questions solved" or "80% accuracy over 40 attempts"), and then just watch the bars fill from the attempts you are already logging.
The reason to start with two is that the value is in the honesty, not the coverage. Seeing the "solid" chapter sit at 60% because your accuracy does not back up your confidence teaches you more than configuring forty chapters you will never look at. Once you trust the mechanism on two chapters, set a sensible subject-level default and let the rest inherit it. You do not have to touch every chapter by hand.
Week four and beyond: bring in the Advisor
By now you have real questions logged, some study hours, at least one mock, and a couple of measured chapters. That is exactly the point at which the Advisor becomes worth using, because now it has something real to reason about instead of generic tips.
Start with plain questions: "which chapter should I prioritise this week and why," "is my accuracy improving or am I fooling myself," "am I spending time on the right subjects." When your Gemini quota runs dry, switch to the Context Builder (bring-your-own-AI) and paste the same grounded context into whatever AI you have open. And when you want the Advisor to know something it cannot compute, your syllabus weightage, your coaching schedule, save it once as an Advisor Library book. But none of that is week-one work. It is the reward for having a few weeks of honest data.
If you want to see how hard the Advisor's grounding actually holds up, Stress-Testing the Advisor (v2) walks through a full real-data transcript.
Fitting LairsFlow around what you already do
Here is the practical part: mapping the study you already do onto LairsFlow, activity by activity. You do not adopt a new routine. You just tag the one you have.
Online live lectures (any platform)
A live or recorded lecture is passive input time, so it does not belong in Practice mode. Two clean ways to capture it:
- The quick way: at the end of the lecture, open the Logbook and add a lecture entry: date, subject, hours, and the topic. One entry, ten seconds, and it feeds your lecture-hours total on the dashboard. This is the lowest-friction option and the one most people should use for live classes, because you are watching the lecture, not babysitting a timer.
- The precise way: if you want the real focused minutes rather than the scheduled length, run a Stopwatch session tagged to that subject while you watch, and pause it when you pause the video. Use this when you care about the gap between "the lecture was 90 minutes" and "I actually paid attention for 55."
Either way, the DPP or practice sheet that comes after the lecture is different: that is question-solving, so those go through Practice mode one question at a time. Lecture in the Logbook, DPP in the timer. That single split keeps your "hours watched" and "questions solved" from ever getting tangled together.
Offline coaching classes
Offline coaching is the same shape as a live lecture, minus the ability to run a stopwatch on your screen. So keep it simple: after the class (or that evening), add a Logbook lecture entry for the hours you sat in class, per subject. You are not trying to time it to the minute; you are recording that three hours of physics coaching happened on Tuesday, so that when the dashboard shows your study time by subject, your coaching load is actually in the picture instead of invisible.
Then the class assignments, the sheets and problems they send you home with, go through Practice mode like any other questions. Coaching hours in the Logbook, coaching homework in the timer.
Self-study and revision
This is where the timer's two study modes earn their keep:
- Reading, note-making, deriving, watching a concept back: Stopwatch, tagged to the subject. Bank the time.
- A fixed focused block, Pomodoro style: Countdown. Pick 25 or 50 minutes and go; it logs the focused time whether the clock runs out or you stop early.
- Solving anything with a right-or-wrong answer: Practice, one question at a time, so it counts toward accuracy, speed, and your chapter completion criteria.
Mock tests
Whatever platform your mock lives on, LairsFlow does not run the test; it remembers it. The evening you take a full mock, open the Logbook, enter per-subject scores and what the syllabus coverage was, and let the overall percentage and the score trend build up over time. This is the one input that tells you whether all the daily logging is actually moving the number that matters.
A realistic day, tagged
Put together, a normal prep day looks like this in LairsFlow, and notice how little it asks of you:
- Morning online lecture on Rotational Motion. Logbook lecture entry afterwards: Physics, 1.5 h, "Rotational Motion."
- The lecture's DPP. Practice mode, each question logged to Rotational Motion.
- Offline chemistry coaching, 2 hours. Logbook lecture entry that evening: Chemistry, 2 h.
- Self-study revision of an old chapter. Stopwatch, tagged to the subject.
- Sunday: a full mock. Logbook mock entry with per-subject scores.
Five small taps spread across a day you were going to have anyway. That is the whole ask. Everything on the Dashboard, every completion bar, and everything the Advisor can tell you is built out of exactly those taps.
The honest bit: what to skip if you are busy
If you take one thing from this post: the non-negotiable habit is starting the timer for question practice. If you do nothing else, that alone gives you a working dashboard and a usable Advisor. Lecture logging, mocks, completion criteria, and the Library all make the picture richer, but they are additions. Skip any of them on a heavy day without guilt. A tracker you use loosely every day beats a perfect system you quit in a fortnight.
The road ahead: this is the last of Vivran, and Chintan is next
A word about where LairsFlow is going, because it changes how you should think about today's release.
Vivran v2 is the final release in the Vivran line. Vivran was about capability: getting the ideas in, the per-question method, the measured completion criteria, the Logbook, the Advisor and its Library, bring-your-own-AI. With v2, the feature set is where it needs to be. The app can now see your whole preparation, active and passive, and reason over it honestly. Adding more surface area is not what it needs next.
What it needs next is depth, and that is the next chapter: Chintan. Where Vivran was about what the app can do, Chintan is about how well it does it. The focus shifts to:
- Security: hardening how your data is stored, synced, and handled, because the more of your real preparation lives here, the more that trust matters.
- Performance: making every screen faster and lighter, especially on the mid-range phones most students actually use.
- UI and UX: taking the six screens v2 introduced and making them calmer, clearer, and more consistent, so a workspace this capable also feels effortless.
In other words, Vivran got the features right; Chintan is about getting the experience right. Nothing you set up in v2 is going away. Chintan builds on exactly this foundation. So the completion criteria you configure, the books you write for the Library, the routine you tag: all of it carries forward. You are not on a version that is about to be thrown out. You are on the version everything after it is built on.
A note from the developer
Lairs.bug
I build LairsFlow alone, and Vivran v2 is the largest thing I have shipped for it. If it feels like a lot, that is because it was a lot to make, and I would rather hand you an honest onboarding path than pretend the whole thing is obvious on day one. It is not. Use the timer, ignore the rest until it calls to you, and let the app earn each bit of your attention.
Closing out the Vivran line and starting Chintan is a deliberate choice. It is easy, and a little addictive, to keep bolting on features. The harder and more respectful thing is to stop, and spend the next stretch making what exists faster, safer, and kinder to use, on the phone you actually own, with the data you actually trust me with. That is the work I am most looking forward to.
Thank you for tracking your preparation here. Every question you log is a small act of honesty with yourself, and that was the whole point from the beginning.
See you in Chintan.
Lairs.bug