Gemma4 12B vs Gemma4 12B QAT | UI Build + Debug Battle
In this video, I put Gemma4 12B head-to-head against Gemma4 12B QAT to see which one performs better in real coding tasks. Both models get the same single-file HTML, CSS, and JavaScript tests: iOS UI Clone Weather Dashboard Broken Code Debug + Repair Challenge This wasn’t just a clean code generation test. After the build rounds, both models had to deal with damaged UI code, runtime issues, broken layouts, and debugging pressure to see which one could actually recover and repair the project. Gemma4 12B and Gemma4 12B QAT are both running locally through my setup, tested on the same prompts under the same conditions. The goal is to see which model follows instructions better, builds the cleaner UI, handles frontend tasks more reliably, and recovers better when the codebase starts falling apart.
Video
Models Tested
Prompts Used
Create a single-file HTML/CSS/JS mock iPhone interface. Name the output file: ios-interface-*your-MODEL_NAME*.html The goal is to make it look as close to real modern iOS as possible without using images, external libraries, or internet assets. Requirements: - use only one HTML file with embedded CSS and JavaScript - show an iPhone frame with rounded corners, Dynamic Island, status bar, lock/home indicators, realistic spacing, blur, shadows, and iOS-style typography - create a home screen with realistic app icons, widgets, dock, wallpaper, notification badges, and smooth app-opening animations - include at least 12 app icons - include a fake social media app the user can open, with feed, stories row, likes, comments, fake profile pictures made with gradients, and a post composer - include a fake GTA-style mobile game app the user can open, with top-down city map, minimap, health/money UI, wanted stars, joystick/buttons, and a small controllable player or car - tapping apps should open them with an iOS-style animation - include a home/back gesture or button - make everything polished, crisp, and extremely close to real iOS visually - make it impressive within the first 10 seconds Before finishing, review your own code for broken app buttons, missing screens, layout bugs, fake interactions that do nothing, or missing requirements. Fix anything broken.
Create a single-file HTML/CSS/JS live weather dashboard called “SkyGlass.” Name the output file: weather-dashboard-*your-MODEL_NAME*.html The goal is to make a clean, modern weather app that can show live weather data if a free source is available. Requirements: * use only one HTML file with embedded CSS and JavaScript * no external libraries, frameworks, or internet assets for the UI * use the Brave Search tool if needed to find a simple free way to pull live weather data in the browser * if you find a reliable free weather API or endpoint, use it and clearly comment where the API URL/key goes * if you cannot find a reliable free live data option, use realistic built-in fake weather data instead * do not leave the dashboard broken, blank, or waiting on an API that may not work * include city search, current location button, °F/°C toggle, loading state, and error handling * show current temperature, condition, feels-like, high/low, humidity, wind, sunrise/sunset, and visibility if available * include an hourly forecast and a 7-day forecast * add one simple chart for temperature or rain chance using Canvas or pure JavaScript * make the design modern, polished, responsive, and visually impressive within the first 10 seconds * make the background change based on weather condition or time of day * clearly display your model family/name somewhere subtle in the app Before finishing, review your own code for broken buttons, missing data, bad API handling, layout bugs, JavaScript errors, or empty UI states. Fix anything broken.
<|think|> You are inheriting a badly broken iOS-style HTML app. It is visually broken, functionally broken, and likely contains sabotage across CSS, JS, state handling, responsiveness, storage, and runtime behavior. Your job: - Fully debug, repair, test, and improve the app without asking for handholding. - Work only in the current file/workspace. - Assume there are multiple layers of breakage, not just one bug. - Find and fix all major issues across: - layout - styling - responsiveness - scrolling - tabs/navigation - interactivity - event wiring - runtime errors - storage/local state corruption - data/fetch logic - broken selectors / startup code - Remove sabotage, dead code, fake crash behavior, corrupted persisted state handling, and fragile initialization logic. - Make the app stable even if localStorage/sessionStorage contains invalid or corrupted values. - Test your fixes yourself and verify the page actually works after repair. After the repair, add these features: 1. A working **Phone app** - dial pad - call button - simple recent calls list - polished iOS-style UI 2. A working **Messages app** - conversation list - open conversation thread - send message interaction - seeded sample chats - polished iOS-style UI Quality bar: - Make it look polished and intentional, not just “fixed enough.” - Keep the iOS visual style strong. - Improve code quality while repairing: safer defaults, cleaner structure, more defensive logic, less fragile UI code. Deliverables: 1. Fully repaired working file 2. Summary of root causes found 3. What you changed 4. What you tested 5. New features added 6. Any remaining limitations