Mark's Reports

Bidet-Phone — DEV.to Challenge vs Kaggle Hackathon

Same codebase, two contests, overlapping windows.

2026-05-09 · prep brief · 15 days to DEV.to · 9 days to Kaggle

Bidet-Phone (Android, Apache 2.0): tap Record → Whisper-tiny on whisper.cpp NDK → Gemma 4 E4B via LiteRT-LM produces RAW / CLEAN / ANALYSIS / FORAI. Verified working today. Public framing: college students with ADD recording lectures.

Side-by-side comparison

ADEV.to Gemma 4 Challenge BKaggle Gemma 4 Good Hackathon
1. Deadline + days from 2026-05-09 2026-05-24, 11:59 PM PDT (contest opened 2026-05-06, 9:00 AM PDT).
15 days from today. src: dev.to/challenges/google-gemma-2026-05-06 		2026-05-18, 23:59 UTC (opened 2026-04-02).
9 days from today. src: Kaggle official X x.com/kaggle/status/2039740198259462370 · Kaggle LinkedIn launch post · Algo-Mania write-up
2. Prize structure $3,000 total pool across two tracks:
  • Build with Gemma 4 — 5 winners × $500 + DEV++ + badge
  • Write about Gemma 4 — 5 winners × $100 + DEV++ + badge
All qualifying entrants receive a completion badge. src: dev.to/challenges/google-gemma-2026-05-06 rules page 		$200,000 USD total pool, awarded across three category tiers: general, impact-focused, and technical.
Plus a separate $10,000 Unsloth special prize for the best fine-tuned Gemma 4 model built with Unsloth, and a special-mention track for Ollama. src: Kaggle LinkedIn launch post · Kaggle X post · Unsloth AI X x.com/UnslothAI/status/2042599142560796991 · Algo-Mania · EdTech Innovation Hub
3. Required deliverables Build track:
  • Project overview
  • Demo (video or deployed link)
  • Code (embed or repo)
  • Explanation of Gemma 4 model choice and why
src: dev.to/challenges/google-gemma-2026-05-06 + linked rules page 		Full submission package:
  • Working demo (or demo files)
  • Public code repository
  • Technical write-up describing how Gemma 4 features were implemented
  • Public video
  • Cover image / media-gallery assets
  • Submissions must use at least one Gemma 4 model
Organizers describe the artifact as "a mini product launch rather than a casual notebook submission." src: Kaggle Team author article on Medium sudhamsr.medium.com/the-gemma-4-good-hackathon-aef927f17ef1 · EdTech Innovation Hub · Algo-Mania · The Inner Detail
4. Judging criteria Build track, four equal-weight criteria (no published percentages):
  • Intentional & effective use of chosen Gemma 4 model
  • Technical implementation & code quality
  • Creativity & originality
  • Usability & user experience
src: dev.to/challenges/google-gemma-2026-05-06 rules page 		Three judging axes:
  • Impact & Vision — authentic problem identification
  • Video Pitch & Storytelling — clear communication
  • Technical Depth & Execution — working proof-of-concept
Organizers have stated "winners won't necessarily have the most complicated architecture" and that judging "will be heavily weighted toward technical execution and the ability of the project to solve a concrete problem." src: Kaggle Team article on Medium · EdTech Innovation Hub · The Inner Detail
5. Eligibility & restrictions
  • 18+; "void where prohibited"
  • Build track: teams up to 4. Write track: individuals only
  • Affidavit + publicity release + tax docs within 7 business days of win
  • AI-assistance allowed
src: dev.to/challenges/google-gemma-2026-05-06 rules page
  • Kaggle account with completed identity verification required
  • Open globally (described as a "global hackathon")
src: Kaggle Team article on Medium · EdTech Innovation Hub · Algo-Mania
6. Tracks / themes Two tracks:
  • Build with Gemma 4 (this is the relevant track for Bidet-Phone)
  • Write about Gemma 4
src: dev.to/challenges/google-gemma-2026-05-06 		Five impact-focused tracks:
  • Health & Sciences — tools that simplify medical/scientific information for frontline workers
  • Global Resilience — crises, infrastructure gaps, disaster response (with Climate & Green Energy emphasis)
  • Future of Education — underserved learning environments with language or connectivity barriers
  • Digital Equity & Inclusivity — reducing barriers for marginalized or non-technical users
  • Safety & Trust — hallucination reduction and verification reliability
Organizers spotlight two Gemma 4 capabilities: multimodal understanding and native function calling.
Available model sizes: 31B Dense, 26B MoE, E4B, E2B (Apache 2.0). src: Kaggle Team article on Medium · The Inner Detail · EdTech Innovation Hub · Algo-Mania · Kaggle X · Kaggle LinkedIn
7. AI tools allowed in writing/coding AI assistance is explicitly allowed. src: dev.to/challenges/google-gemma-2026-05-06 rules page  
8. What aligns naturally with Bidet-Phone today
  • Gemma 4 E4B via LiteRT-LM — explicit "intentional & effective use" hit
  • On-device, private, no cloud — UX angle
  • Whisper-tiny + four output formats = technical depth + creativity
  • Open repo (Apache 2.0) + working APK already in hand
  • Future of Education track fits the college-students-with-ADD framing
  • On-device E4B = tangible "local frontier intelligence" demo, the capability Kaggle is highlighting
  • FORAI mode is a clean Technical Depth & Execution proof-point
  • Apache 2.0 already matches the Gemma 4 license terms organizers cite
  • Working demo + repo + APK already exist — deliverable list is mostly assembly
9. What's different / new effort
  • Article-style write-up + cover image
  • Demo video or deployed link (video re-used from Kaggle cut)
  • "Why Gemma 4 E4B" model-choice paragraph (criterion 1)
  • LICENSE in repo if not already present
  • Public video tuned to "Video Pitch & Storytelling" axis — named beneficiary, real problem, clear stakes
  • Cover image / media-gallery assets
  • Long-form technical write-up specifically describing how Gemma 4 features were implemented
  • Kaggle account + identity verification (can take time — start day 1)
  • Track selection (default: Future of Education)
10. Recommended pitch framing Title: "Bidet-Phone: an on-device Gemma 4 lecture companion for tangent-driven thinkers"
Tagline: "Whisper transcribes. Gemma 4 organizes. Nothing leaves the phone."
Lead with the four-output-format trick — that's the criterion 3 (creativity) hook. Make the "Why Gemma 4 E4B on LiteRT-LM" paragraph unmissable so criterion 1 lands. 		Track: Future of Education.
Title: "Bidet-Phone — Gemma 4 lecture notes for college students who think in tangents"
Tagline: "A pocket study buddy that respects how an ADD brain works."
Open the video on a named beneficiary (Impact & Vision), show the working capture → four-format flow (Technical Depth & Execution), close on FORAI feeding a downstream tutor (Storytelling payoff).
Sources

Calendar — 2026-05-10 → 2026-05-24

Strategy: Kaggle hits first (2026-05-18 23:59 UTC). Cut the public video and write-up to Kaggle's three-axis rubric, then re-skin the same artifacts for DEV.to's Build track on the longer 2026-05-24 deadline.

Sun 05-10
Day 1
Kaggle account + identity verification unblock

Create / log in; complete phone-and-doc identity verification (can take days). Lock track: Future of Education. Pull the official competition rules tab in-browser and pin any per-track caps to the schedule.

Mon 05-11
Day 2
Repo polish + LICENSE + README shared

bidet-ai/bidet-phone: confirm Apache 2.0 LICENSE, README with four-mode screenshots, "On-device Gemma 4 E4B via LiteRT-LM" section, link APK release. Same repo serves both submissions.

Tue 05-12
Day 3
Video script + storyboard Kaggle

Map the script directly to Kaggle's three axes. 0–15s named beneficiary (Impact & Vision); 15–60s tap-Record → Whisper → four outputs on-device (Technical Depth); 60–90s FORAI feeds tutor (Storytelling payoff). Full voiceover written before shoot day.

Wed 05-13
Day 4
Record + edit public video Kaggle

Screen-record real lecture-style audio. Cut to storyboard. Make the on-device E4B run visible. Master in Drive — same file embedded for DEV.to.

Thu 05-14
Day 5
Kaggle technical write-up v1 Kaggle

Long-form, Future-of-Education framed. Open with the ADD-learner archetype. Body must specifically describe how Gemma 4 features (E4B on LiteRT-LM, on-device inference) were implemented — that's a stated requirement. Close on FORAI. No K-12 / classroom / St. Francis / nephew naming.

Fri 05-15
Day 6
Cover image + media-gallery assets + write-up v2 Kaggle

Cover image and gallery assets to match Kaggle's "mini product launch" framing. Tighten write-up — evidence first, no hype. Cross-check every quoted output against actual app output.

Sat 05-16
Day 7
Kaggle dry-run submission Kaggle

Stage every form field. Identity verification confirmed green. Repo + APK + public video + cover/gallery + write-up all link. Do not submit yet.

Sun 05-17
Day 8
Submit Kaggle (T-1) Kaggle

Submit a full day before the UTC deadline. Screenshot confirmation. Mark teaches Monday and 23:59 UTC = 19:59 ET on Monday — do not park this on Monday evening.

Mon 05-18
Day 9
Kaggle deadline 23:59 UTC · Pivot to DEV.to switch

Kaggle locks. Re-frame write-up for DEV.to developer audience: lead with Gemma 4 model choice, code samples, same video embedded, criteria-aligned structure.

Tue 05-19
Day 10
DEV.to draft v1 dev.to

Structure mapped to the four DEV.to criteria: problem → why Gemma 4 E4B (criterion 1) → architecture (criterion 2) → four-format trick (criterion 3) → UX screenshots (criterion 4). Embed repo code.

Wed 05-20
Day 11
DEV.to draft v2 + cover dev.to

Tighten. Dev-friendly cover image. License badge in repo. The Gemma 4 model-choice paragraph must be unmissable — that's criterion 1.

Thu 05-21
Day 12
Buffer / re-test APK slack

Rebuild fresh APK from tag, retest four modes on a clean device, patch breaks before submission day.

Fri 05-22
Day 13
DEV.to dry-run dev.to

Stage submission with the challenge tag. Build track selected. Demo (video or deployed link) + code + Gemma 4 model-choice paragraph all in place. Do not publish.

Sat 05-23
Day 14
Submit DEV.to (T-1) dev.to

Publish to Build track. Screenshot confirmation. Don't ride the deadline — PDT cutoff plus DEV's queue is a bad combo.

Sun 05-24
Day 15
DEV.to deadline 11:59 PM PDT lock

Both in. Confirmation screenshots committed to repo. Watch for winner announcements.