Academic Year Planner
AY2026/27
AYPlanner M2.6.1.5.1 · Full pairing lineage inventory hotfix
Mobile App Status
Tap to expand connection, offline and install details
Ready
Installable PWA · offline shell · encrypted sync readiness
ConnectionChecking…
Secure contextChecking…
Offline cacheChecking…
Installed modeChecking…
This device is ready for encrypted M2 pairing/sync. Use AYPlanner's in-app ‹ Back control for reliable navigation; Android's hardware Back behavior is controlled by the installed PWA/browser and may still exit the app. Import a Desktop Pairing package from Sync, or use the legacy M1.1 snapshot import only for older snapshot files.
Today

A phone-first summary of what needs your attention.
Tasks at a Glance
0 open

Next

Needs Attention

Upcoming Trip

Agenda is intentionally the primary mobile calendar view. Month view can be added later if useful.

Agenda

Tasks

Inbox

Use Inbox when you do not yet know whether something should become an Event, Task, Trip note or Exam item.

Trip Mode

Mobile Sync

Enter the password before importing or exporting. It is used only for this operation and is not stored.
Not paired
Pending0changes
Conflicts0open
Full Pairing lineage—tracked / baseline
Baseline lineage missing—records
Local-only / legacy—not in latest Full Pairing
Latest Full Pairing—current records
Lineage note: Baseline lineage is measured only against the latest imported Full Pairing package. Local-only / legacy records are present on this phone but absent from that Desktop baseline; AYPlanner does not delete them automatically.
For M2, choose a file whose name ends in .aypsync. An .aypsync package is an encrypted JSON envelope internally, so some devices may describe its file type as JSON. Files actually named MobileCompanion_*.json belong to the older M1.1 snapshot workflow.
Routine Sync
If this phone is already paired, import Desktop Changes / Reply and export your Mobile changes.
Legacy M1.1 Snapshot Import
This is the older one-way snapshot workflow and clears M2 pairing metadata.
Conflicts
No conflicts.
M2.6 Secure Online Relay Preview
Not configured
Routine sync can use Firebase Auth + Firestore instead of moving .aypsync files. The relay stores only the already-encrypted AYPlanner wrapper plus limited routing metadata. Initial Full Pairing remains a one-time manual step.
Cloud relay is not configured yet.
Controlled Auto Sync
Runs only while AYPlanner is open, signed in and armed for this session.
Not armed
StateIdle
Next remote checkManual
Last successful contactNever
Retry / conflictsNone
Last transfer: None yet
Mobile pending revisions: 0
Enable Auto Sync, sign in, enter the AYPlanner sync passphrase above, then arm this session.
Firebase account password and AYPlanner sync passphrase are not stored. The passphrase used for Auto Sync is kept only in memory and is discarded when the PWA closes, signs out or is disarmed. New Mobile changes are pushed shortly after saving while the PWA is active. Android may suspend web-app timers in the background; returning to AYPlanner triggers the return-to-app sync after 5+ minutes away.
M2 sync packages are encrypted. Passwords are never stored. Attachments and Private/Hidden records are not part of this foundation.
Reset this Mobile Companion
Clears this phone/browser's AYPlanner data, pairing, pending sync, conflicts and snapshot metadata. It does not affect Desktop.

Quick Add