DefenceSelf-submittedNot a finalist (self-declared)

Resque

KaczkiRatowniczki · leeree1/Resque

Council score

Median of 3 models, weighted by the task's official criteria
63.0 / 100

A well-themed, largely real one-hop offline SOS app whose Nearby plumbing and offline-first design genuinely exist in code, but the multi-hop mesh and central-sync claims are unimplemented, no demo evidence proves it ran, and safety hygiene around fake responder ACKs and exposed victim data falls short of a life-safety pitch.

Criteria · line = median, dots = each member
Idea & Innovation30%
6.0

The gap is real and concretely reasoned, with thoughtful touches like per-field data minimization, stealth mode, QR fallback and a CPR metronome. But offline mesh messengers already exist (Bridgefy, Briar, Meshtastic) and the claimed multi-hop relay is not delivered, so novelty stays moderate.

Relation to Category20%
8.0

Unanimous fit: communication when infrastructure fails, with buffering, ACKs and a first-aid module, and no off-category filler in the repo. The median reflects strong fit tempered only by the unproven degraded scenario.

Members disagree here: scores range by 2.0 points.
Practical Applicability / Usability20%
5.0

One-tap SOS with alarm, strobe and honest error states is usable under stress, but members split 7 to 3 here. The evidence supports the skeptical side: the relay never re-broadcasts, the gateway button deletes local data instead of syncing, adoption bootstrapping is unaddressed, and no demo proves the app ran on hardware.

Members disagree here: scores range by 4.0 points.
Design (visual/UI)20%
7.0

Code and deck show a coherent dark tactical theme with glanceable status colors, pulse animations, honest disabled states and a clean four-tab layout. But all 35 screenshots are undescribed and the deck is image-only, so polish is inferred rather than verified.

Members disagree here: scores range by 2.0 points.
Completeness & Implementation Value10%
5.0

There is 5.3k LOC of real Dart with a genuine Nearby Connections path, permissions, dedupe, ACKs and offline storage. But the multi-hop relay is absent from the code, the cloud leg is a simulate button, and only 2 trivial tests exist, landing the median mid-scale.

Members disagree here: scores range by 4.0 points.
Source lines5,332
Tests2 cases
Claims built6.0 / 10
Task fitYes

Strengths

  • Real Google Nearby Connections integration (advertising, discovery, connection, payloads) with permission requests and error-code handling, not a stub.
  • Offline-first architecture: packet buffering in local storage, TTL'd flush design, and GPS failures falling back to defaults with clear status text.
  • Degraded-mode extras suited to crisis use: stealth mode, torch strobe, alarm audio, QR sharing, and searchable offline first-aid protocols.
  • All 31 commits by 5 authors inside the event window, with a coherent crisis UI across the SOS, Radar, Sztab and Apteczka tabs.

Weaknesses

  • The headline multi-hop mesh is not in the code: onPacketReceivedFromPeer stores, increments hopCount and ACKs but never re-broadcasts, so each node reaches only direct peers; the shared code-level reading of A and C is better supported than B's claim of working relay.
  • The internet gateway is a mocked integration: the 'simulate connection' button and flushToCentralServer clear local storage without ever calling FirebaseSyncService, so the central-sync claim is unimplemented.
  • No demo, video or runtime evidence verifies the mesh ever ran on hardware, and the 35 screenshots are undescribed, so the required working degraded-scenario demonstration is effectively missing.
  • The README is the untouched Flutter template so nobody outside the team can build it, only 2 trivial test cases exist, and the hardcoded packet id '1842' on the broadcast screen would collide with the app's own dedupe on any repeat SOS.

Red flags

  • Every receiving phone auto-replies with an ACK signed 'RATOWNIK_PSP' stating the report was accepted, faking official responder confirmation in a life-safety app.
  • The Firebase Realtime Database is documented in-code as publicly readable and carries victim GPS locations, with API keys and google-services.json committed to the repo.
  • The gateway 'simulation' silently deletes local packets instead of uploading them, which in real use would destroy undelivered SOS data.
Built during the event: yes: 31 commits by 5 authors, 2026-10-03 12:40 to 2026-10-04 06:22 UTC
Live demo: none found in the form or README
Council v9
Aclaude:glm-5.3-flash63.0100% agree
Bdots-studio/dots-3-note-preview:free76.060% agree
Cinclusionai/ling-3.0-flash-sante:free53.070% agree
Jclaude:glm-5.3–judge
Self-submitted and unverified: the result shown is the team's own claim. The council read an evidence pack built from the repo, its decks and docs; it didn't run the code or see the pitch.
The site is open source

The council, the evidence pack, the prompts and the queue are all on GitHub. If a review helped you, a star helps other teams find it.

Star on GitHub