Thiru-tenext
06fa6b797a
The effort pass, end to end. Every screen was run through one test — if I remove this sentence, does the customer make a worse decision? — and the parts that failed it are gone. The flow Home ▸ BOOK ▸ Where is it going? ▸ When shall we collect? ▸ details ▸ booked BOOK opens a sheet, not a form. The destination is browsed state-then-district because a flat list of every serviceable district survives twelve and not sixty, and search cuts across states because somebody who knows they are sending to Chennai should not have to know which state it is in. Districts multi-select, but only where the server allows it: BookingLimits advertises maxDestinations: 1 until the Miler build keys on consignmentid, and a sheet that ignored that would sell a booking the network cannot complete. The pickup window is now a step the customer answers rather than a slot chosen for them. A pickup window is a promise about somebody's afternoon. What the screens stopped saying Home lost the orb caption for returning customers and a four-cell live card. Send lost the city strip, both address fields, the optional disclosure and three sentences about charging — the route, the packages and the button are what is left. Tracking lost a radar with a bike in it, a Milers-in-your-zone count, a "Step 2 of 7" and a sentence describing the screen you were looking at. The window sheet lost "Fastest pickup", "4 Milers nearby" and "Relaxed evening handover". Type Poppins, which has no variable release — four static cuts, and the sans styles set fontWeight alone because fontVariations on a static font is ignored in silence. Every weight dropped a step and the tracking went deeper: Poppins is built on near-circles and carries more ink than the humanist faces before it. Objects One lit sphere on Home, and the primary button now takes its gradient and rim because a committing action that is not lit like the hero reads as a different material. The tracking rail's connector is crimson as far as the parcel has come, so the line is the progress bar. Confirmation is a white tick on green: crimson is this app's action colour and that screen has nothing left to do. Bugs found on the way The OTP screen dropped digits. Four fields passing focus along lose a keystroke that arrives mid-transition, so "1234" became "124" and the screen answered "That code did not match" — blaming the customer for its own race. One field now, four boxes that only draw. Nothing ever asked for the customer's location: detectPickupLocation was the OTP screen's job, so a restored session or an auto-login never triggered the permission prompt and the pickup map had nothing to centre on. The launcher icon and both splash screens pointed at a house drawn as two vector paths — a placeholder that shipped. The splash clock started when the widget was built rather than when it was visible, so the truck got 0.45s of a 1.8s beat behind Android's own splash. It waits on waitUntilFirstFrameRasterized now, raced against a timeout so a binding that never reports one cannot strand the app. Also: design/screens/ holds all 19 screens under readable names, tool/ has the scripts that refresh them and rebrand the Lottie, and DESIGN.md is current. flutter analyze clean. 88 tests, 1 skipped. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EqVJPB9B4QuieZnBAAKgYQ
47 lines
2.2 KiB
Dart
47 lines
2.2 KiB
Dart
import 'package:flutter/widgets.dart';
|
|
import 'package:lucide_icons_flutter/lucide_icons.dart';
|
|
|
|
/// A glyph per state, keyed by the backend's state code.
|
|
///
|
|
/// ── Why the state and not the district ──
|
|
///
|
|
/// The first version of this marked every *district*: Chennai a capital,
|
|
/// Coimbatore a factory, Tiruppur knitwear, and so on down a flat list of
|
|
/// twelve. It scanned well at twelve. It does not survive sixty — and more to
|
|
/// the point, it put the app in the business of having an opinion about every
|
|
/// district in India, which is a table nobody can keep honest and a mistake
|
|
/// somebody eventually finds offensive.
|
|
///
|
|
/// There are twenty-eight states. Giving each one a mark is a bounded problem,
|
|
/// the marks stay recognisable, and the district list underneath is left as
|
|
/// what it should be: names and delivery promises, nothing competing with them.
|
|
///
|
|
/// ── The rule each glyph follows ──
|
|
///
|
|
/// One thing about the place that a person living in India would recognise,
|
|
/// and never a religious building — a temple state drawn as a church is worse
|
|
/// than no icon at all. These are editorial choices, not data: they are meant
|
|
/// to be argued with and changed, which is why they are one table in one file.
|
|
///
|
|
/// ── The fallback is the contract ──
|
|
///
|
|
/// [stateMark] answers for every code, including ones that do not exist yet.
|
|
/// The serviceable list is the backend's, so a state opened there appears here
|
|
/// immediately — with the pin, looking deliberate, until somebody adds a line.
|
|
/// Nothing renders blank and nothing throws. Adding a state is one entry;
|
|
/// forgetting to is not a bug.
|
|
const Map<String, IconData> _marks = {
|
|
'TN': LucideIcons.landmark, // the gopuram silhouette
|
|
'KL': LucideIcons.treePalm, // the backwaters
|
|
'KA': LucideIcons.crown, // the Mysuru palace
|
|
'AP': LucideIcons.mountain, // the eastern ghats
|
|
'TG': LucideIcons.castle, // the Golconda fort
|
|
'MH': LucideIcons.ship, // the Bombay harbour
|
|
'GA': LucideIcons.sailboat,
|
|
'PY': LucideIcons.waves,
|
|
};
|
|
|
|
/// The mark for a state code, or a pin for one nobody has named yet.
|
|
IconData stateMark(String? stateCode) =>
|
|
_marks[stateCode] ?? LucideIcons.mapPin;
|