DEV Community

Cover image for I Made Tyre Size Detection App Using Gemma4:e4b

I Made Tyre Size Detection App Using Gemma4:e4b

Gemma 4 Challenge: Build With Gemma 4 Submission

This is a submission for the Gemma 4 Challenge: Build with Gemma 4

What I Built

NewTyre-AI is a secure, localized full-stack web application designed to automate a deceptively complex industrial task: passenger vehicle tyre sidewall size extraction.

The Problem

Traditional computer vision pipelines frequently default to cloud-dependent architectures to process visual data. While convenient, this approach introduces persistent operational liabilities for businesses: recurring cloud API bills, data transit latencies, and corporate data privacy exposure. Furthermore, reading alphanumeric characters from a tyre sidewall is difficult for traditional linear Optical Character Recognition (OCR) tools because text printed on rubber is non-linear, low-contrast, heavily textured, and curved.

The Solution

NewTyre-AI solves this by shifting the entire visual processing workload onto a local, physical on-premise company server. The system ingests sidewall photos, filters them through a localized multimodal edge model, and returns an un-hallucinated, deterministic 9-character tyre size code (e.g., 205/60R16) to the technician with zero ongoing cloud compute or external API costs.

Demo

Video Demo(30 sec): Google Drive

Code

GitHub Repo

How I Used Gemma 4

For this project, I deliberately selected the Gemma4:e4b (Effective 4B) parameter model rather than scaling up to the massive dense weights or downgrading to the highly lightweight e2b version. 2B model lack the visual cross-attention layer density required to accurately map characters in noisy geometric layouts, while 32B model is a overkill. The e4b model retains the precise structural transformer resolution required to read curved, dirty text on dark rubber cylinders without throwing a wave of false positives.

Top comments (0)