Bitácora

Español · Build and tests

A Flutter app for six fictional field tasks. Search and filter the list, read a task’s instructions and mark it complete. Completion is saved on the device and restored after a restart.

The project shows asynchronous state, superseded requests, confirmed writes and recovery from storage failures. The task list ships with the app. No account, API key, location or backend is needed.

1. Open a task, read its instructions and select Mark complete.
2. Return to the list and compare All, Pending and Completed. Search by title; Spanish searches accept unaccented vowels.
3. Open Loading scenarios with the science icon. Select Simulated failure or Slow response. The bundled tasks remain available.
4. Choose Normal loading to recover.
5. Restart the app to check that completion remains saved.

If saved status cannot be read, completion controls stay disabled and the app does not show a guessed completion count. If a write cannot be confirmed, the screen keeps the last confirmed state. Reload tasks reads the saved status before another attempt. Controller and widget tests exercise these failures without damaging real storage.

Checked with Flutter 3.38.7 / Dart 3.10.7, JDK 17 and Android SDK 36. Android requires API 24+. Versions and dependency hashes are recorded in pubspec.lock.

flutter pub get --enforce-lockfile
flutter analyze
flutter test
flutter run --flavor dev
flutter build apk --debug --flavor dev
flutter build apk --release --flavor prod
flutter build web --dart-define=APP_ENV=dev --no-web-resources-cdn --pwa-strategy=none

Both dev and prod are demos. Android gives them different application IDs and launcher names, so they keep separate local storage. Both use lib/main.dart. APP_ENV selects the web environment label; it does not select a live service. Unknown environment names fail explicitly. To generate an AAB, use flutter build appbundle --release --flavor prod.

Flutter may select Android Studio’s JDK before JAVA_HOME. Use JDK 17 for this project through local Gradle configuration or GRADLE_OPTS=-Dorg.gradle.java.home=/path/to/jdk-17. Keep local paths and signing keys outside version control. Production signing is not configured.

Replace DEVICE_ID with the target serial:

flutter test integration_test/app_test.dart --flavor dev -d DEVICE_ID
flutter drive --driver test_driver/capture.dart --target integration_test/app_test.dart --dart-define=CAPTURE_SCREENSHOTS=true --flavor dev -d DEVICE_ID --keep-app-running

The integration test resets only this demo’s completion IDs, recreates its controller and leaves one fictional task completed. The opt-in driver writes the two PNGs in docs/images/. Run Flutter build/test/drive commands sequentially in one checkout because they share generated Android files. For a normal-process restart check after an integration build, rebuild or reinstall the normal entry point without clearing its preferences; see verification.

• tasks.dart: models, source/store contracts, request generations, time limit and confirmed completion state.
• completion_preferences.dart: SharedPreferencesAsync adapter, storing only completed task IDs.
• main.dart: dependency construction, board/detail navigation, controller ownership and recovery actions.
• copy.dart: Spanish/English resources with English fallback for unsupported languages.
• controller_test.dart: failures, late results, disposal, timeout and read-only state.
• widget_test.dart: navigation, filters, storage recovery, resizing and enlarged text.
• app_test.dart: actual Android preferences and optional captures.

Architecture explains why ignoring a superseded Future differs from cancelling transport, and why storage reads must succeed before editing. DESIGN.md records the layout, independent row actions and locally bundled Outfit font.

There are 26 controller/widget tests: 17 controller and nine widget cases, including English/Spanish read/write recovery at 360×800 with 1.8 text scaling. Verification separates the latest local runs, native persistence, browser checks, artifact audits and any failed attempts. The workflow runs Android/web checks and a separate API 35 integration job.

The source export includes Android and web. Native iOS and physical devices have not been validated. Release enables R8/resource shrinking, but there is no production signing or store release. Artifact audits are advisory. Widget/emulator checks are not a formal accessibility certification.

Original application code, text, data and vector artwork: MIT, Manuel Naval, 2026. Flutter shells, fonts and dependencies retain their licenses in third-party notices.