Worked out in your browser. Nothing you enter is sent anywhere.
The number nobody calculates
Every baby sleep tool asks about one baby. With twins that is the wrong unit. What determines whether you get a break is not when each baby sleeps but whether the two naps intersect, and two long naps that miss each other are worth less to you than two short ones that line up.
So the useful question is not "when is the next nap", it is "when are they both down". That is what this works out.
Why the fix is in the morning
When the naps miss, the instinct is to push the later baby's nap earlier. That usually fails, because a baby who has not been awake long enough will not go down, and you end up with a fight instead of a nap.
The lever that works is the wake-up. Both babies' wake windows start when they wake, so moving one wake-up moves everything downstream of it. Wake the twin who is running late, by 15 or 20 minutes at a time over a few days, and the naps converge on their own. That is why the tool gives you a morning number rather than a nap time.
What it does not know
It uses age-average wake windows and nap lengths, and your babies are not averages. It also cannot see a tooth coming through, a growth spurt, or the twin who has decided that 4am is morning now. Treat the output as a starting position for the week rather than a timetable, and trust a pattern you have actually observed over the one the tool assumes.
Where the app fits
Doing this once is arithmetic. Doing it every day, for both babies, while holding at least one of them, is why it stops happening by the second week. Multibaby logs each wake and nap for both babies by voice and shows the overlap as it happens, so the number is there without you working it out at 6am.