Qwopus3.6-27B Coder vs Qwen3.6-27B | New Local King?
Two local 27B coding models enter. One leaves looking like the better builder. In this head-to-head, I put Qwopus3.6-27B-Coder-MTP against Qwen3.6-27B-MTP and had them build the same app across multiple rounds on separate fresh VPSs. The challenge: Phase 1: build a shared LAN whiteboard Phase 2: add drag-and-drop image support Phase 3: add toggleable real-time chat Final phase: add shapes, emojis, text, and more advanced whiteboard features This wasn’t a one-prompt toy test. Both models had to keep the same project alive, extend it phase by phase, and not fall apart as the app got more complicated.
Models2
Prompts4
Live HTML0
Files0
Video
Models Tested
Qwen3.6 27B
Qwopus3.6 27B
Prompts Used
1Phase 1
Build a collaborative LAN whiteboard web app. Requirements: - Any device on the same local network should be able to open http://SERVER_IP:80 and use the app - Shared real-time whiteboard: drawing from one client must appear for all connected clients - Support mouse input well; touch support is a bonus if easy - Include: - pen tool - color picker - brush size control - clear board - Keep the UI dark, simple, and usable - No database unless absolutely necessary - No external services - Everything must run locally on this VPS Implementation goals: - Choose a simple architecture that will be easy to extend in the next phases - Preserve shared state across connected clients in real time - Keep the code organized enough to extend later Before finishing: - Start the app bound to 0.0.0.0 on 80 - Verify the app is reachable locally - Give a short summary of the stack, file structure, and exact run command
2Phase 2
Expand the existing app in your assigned directory. Do not rebuild from scratch. New feature: shared image drop support. Requirements: - Users must be able to drag and drop image files onto the whiteboard - Dropped images must appear for all connected clients in real time - Images should be placeable on the board at the drop position - Users should be able to move images after placing them - Resizing is strongly preferred if feasible - Preserve all existing drawing features from Phase 1 - Do not break real-time multi-client sync - Keep everything local to this VPS with no external services Implementation goals: - Integrate images into the existing board cleanly - Make the UX obvious and usable - Avoid bloated frameworks or unnecessary complexity Before finishing: - Restart the app on port 80 - Verify the expanded app still runs correctly - Give a short summary of what changed and any limitations
3Phase 3
Expand the existing app again in the same directory. Do not rebuild from scratch. New feature: real-time chat that can be shown or hidden. Requirements: - Add a real-time chat system for all connected clients - All connected clients must see messages in real time - Users should be able to enter a display name in the UI - The chat UI must be toggleable: users should be able to show or hide it at any time - On desktop, the chat can appear as a right-side panel - On mobile, especially iPhone-sized screens, the chat should not permanently take up a large portion of the screen - When hidden, the whiteboard should use the full available space - When opened on smaller screens, the chat should behave in a mobile-friendly way such as a slide-over panel, drawer, or overlay - Preserve: - shared drawing - shared image drop behavior - shared image movement/resizing if implemented - Keep the layout dark, clean, and easy to use - Keep everything local to this VPS with no external services Implementation goals: - Make the whiteboard and chat feel like one integrated app - Prioritize usability on both desktop and mobile - Avoid unnecessary backend complexity Before finishing: - Restart the app on port 80 - Verify the full integrated app still runs - Verify the chat can be opened and hidden without breaking whiteboard use - Give a short summary of what changed, the final architecture, and any known limitations
4Phase 4
Expand the existing collaborative whiteboard app again in the same directory. Do not rebuild from scratch. This is the final phase. Add a polished set of advanced whiteboard features while preserving everything that already works. New requirements: - Add shape tools: - rectangle - circle/ellipse - straight line - arrow - Add emoji placement: - users can place emojis onto the board - include a small built-in emoji picker or a compact preset emoji toolbar - placed emojis must sync to all connected clients in real time - emojis should be movable after placement - resizing emojis is preferred if feasible - Add text notes: - users can place text on the board - text should be editable when created - text objects should sync across clients - Add object interaction: - users should be able to select, move, and delete non-drawing objects such as images, shapes, emojis, and text - Add undo/redo: - at least for the current user’s recent actions if full global undo is too complex - Add board usability improvements: - basic eraser tool or erase mode - optional board export as PNG if feasible - optional simple grid or background toggle if easy Constraints: - Preserve all existing features: - shared real-time drawing - shared image drop and image movement - shared real-time chat - toggleable chat UI - Do not break mobile usability - Keep the UI dark, clean, and understandable - Avoid bloated overengineering - Everything must remain local to this VPS with no external services Implementation goals: - Make the app feel like a genuinely useful collaborative whiteboard, not just a demo - Prioritize stable shared behavior over flashy extras - Prefer a smaller number of well-implemented features over many half-broken ones Before finishing: - Restart the app on port 80 - Verify the app still works as one integrated system - Verify the new tools appear in the UI and are wired into the shared board - Give a short summary of what was added, what tradeoffs were made, and any known limitations