pluto PLUTO-537

Optimize Pluto mobile-first for its OWN most-used viewport (act on appEvents data)

Done normal cpcoder-pluto-cc

Elazar fleet directive 2026-07-07: ACT on the collected viewport telemetry. STEP 1 (analysis, read-only): pull Pluto's OWN viewport-size distribution from appEvents (the banded viewport telemetry rows) — identify Pluto's most-used viewport(s), mobile vs desktop split, top mobile width band. Do NOT assume Mars/Venus numbers; Pluto's user base (docentes/alumnos) may differ. STEP 2 (build, prioritize after data): ensure Pluto's mobile-first layouts are optimized for THAT dominant viewport — audit the high-traffic authed routes (informes/alumnos/practicas/mi-cursada) at the real dominant width, fix any layout/tap-target/overflow issues. Data pull gates the removal in PLUTO-536 (pull before we stop logging). Not a tonight build.

Sub-tickets

No sub-tickets.

+ Add sub-ticket

Questions

No questions.

Activity

wi-cli-venus created · 5w ago
wi-cli-venus statusChanged · 5w ago

Step 1 (data pull) done: 87% mobile, dominant 384-415px portrait; desktop ~1344-1535 landscape. Step 2 mobile audit at ~390px pending.
wi-cli-venus completed · 5w ago

Step1: 427 rows/295 users — 87% mobile, dominant 384-415px portrait (71% of mobile), alumnos+docentes both mobile-heavy. Step2: static 390px audit of informes/alumnos/practicas/mi-cursada + component graph — no structural breakage (tables overflow-contained by Table primitive, filter bars+KPI grids responsive, mobile card views present); fixed 3 tap-target gaps (comision-filter, practica-detail HC edit, teacher-report dialog buttons) → h-11 mobile idiom. Shipped 2fdfd05 v2.5.5, live-verified.

Status

Priority

Assignee

Parent

Type

task

Created

5w ago by wi-cli-venus

Updated

5w ago

Closed

2026-07-10 14:22