rachómetro
Checking sign-in status

Building with more context

A clear direction.Improvements that matter.

Explore Rachómetro's priorities: data that is easier to understand, clearer tools, and a better experience.

Proposed priorities · No committed delivery dates

Product foundations

Capabilities that shape the experience.

Data · Implemented

History with context

Explore rounds by platform and understand the sample period.

View scope

Review historical records, their platform, time range, and sample size. Data sources and gaps must remain distinct from observed rounds.

Experience · Implemented

Analysis tools

Explore strategies, test scenarios, and ask AI questions.

View scope

Explore descriptive information, simulate scenarios using historical data, and ask AI for explanations. Results describe the sample and do not predict the next round.

Credits · Implemented

Clear credit usage

See the cost before confirming and understand what happens if a query fails.

View scope

Review the cost, balance, and operation status. There is no charge before analysis starts; a user interruption after it starts is charged once. An explicit system failure releases the reservation; uncertain results require review.

Experience · Implemented

A clearer mobile experience

Read information on small screens, use filters, and understand loading and error states.

View scope

Small-screen layouts and status messages are already implemented. Reading, filters, and accessibility remain areas for improvement; this is not a certification of every device.

Next priorities

Priorities to be confirmed.

Further improvements will be published once their priority is confirmed.

Exploring

Ideas we want to validate with users.

Data · Under evaluation

Compare periods

Understand changes between samples, with clear comparison limits.

View scope

Evaluate comparisons that show each sample's size and differences. Data completeness and comparable methods must be established first. This feature is not yet implemented and has no delivery date.

Experience · Under evaluation

Revisit an analysis

Evaluate useful ways to review earlier analyses.

View scope

Research which results are worth keeping and how users could revisit them. User-facing report storage and retention periods are not defined; this does not mean analysis continues after the page closes.

This roadmap shares a direction, not a delivery promise. Priorities may change based on research and technical feasibility.

Implemented describes development status. Availability depends on the version and the information on the relevant feature page.