How DeepSeek builds in Taskade Genesis

Won on design: the only model that looked right in both light and dark, ran without a single error, and laid out cleanly on a phone screen.

Won on design again, and this time the finished workspace saved real data with light and dark themes both working throughout.

Fastest and cleanest run on the 32-question client sign-up form: 12 minutes 36 seconds.

Finished the tracker and made both follow-up changes cleanly, but its long-form build ran out of time.

Built the richest sales CRM of the test, with six pages and a scoring automation that scored all 7 sample leads.

Built a four-page match tracker and said plainly that its weekly recap was still switched off.

Typed all 32 client sign-up questions and built a 48-field submissions table, then ran out of time before finishing.

Built a three-page fleet inspection app for 42 vans where the brief named 40.

Its recipe box came out as a printed cookbook with 13 recipes, four pages, and both automations live.

Built a three-page match tracker whose coaching automation ran on the first match logged and wrote a note back into that match about six minutes later.

Built a two-page family intake form that saved every answer and both photos, and its alert automation ran twice. The build ran past the test time limit.

Added the new teacher question and put the change live.

Built the family intake form in 7 minutes 25 seconds so it saved every answer and both photos, and its new-family automation ran. Three sample families showed on the teacher page as if they were real.

Added the new teacher question as an optional field and kept it off the printed summary sheet, and said so.

Built a five-page Dota 2 match tracker with labeled sample matches, but every hero showed as unknown and no match could be saved, while its summary said the save had been checked.

Rebuilt the 32-question client sign-up form with all 32 questions word for word and a scoring guide, but the form saved each answer one question off, so every submission was rejected.

The richest workspace of the test: 8 automations, a record 60 fields, and all four builds word for word.

Won the tracker test as the most efficient app that opened. Two stronger-looking results could not be used, so they did not receive a score.

Went from none of its four builds matching the brief to all four word for word on a shorter prompt. The biggest jump we have measured in a single test.

A complete match tracker that saved every detail.

Built the deepest lead table of the sales CRM test, with 12 fields per lead, then put its one-page board behind a sign-in screen.

Finished the client sign-up form with all 32 questions word for word and left both automations switched off.

Spent the fleet-inspection test building data and automations and wrote no page.

Built a complete match-tracker data layer, then put the app behind a sign-in screen.

Built one of the two best-looking match trackers of its test, with a win-rate trend chart in light and dark, in 36 minutes, but its hero picker listed only 17 heroes.

Built the family intake form in 7 minutes 24 seconds so it saved every answer and both photos, and the new teacher question landed. Two sample families showed as real, and its summary did not mention them.

Built a Dota 2 match tracker with a win-rate trend that saved a logged match and added the heroes page when asked. About 15 sample matches showed as real.

The test time limit ended the family intake build before a closing summary. The follow-up message finished the app and added the new teacher question.

The finished form saved every answer and both photos, and the teacher page started empty instead of showing made-up families.

Built the best-looking Dota 2 match tracker of its set, and a logged match saved. The time limit ended the build, and the follow-up message finished the interface and the heroes page.

The test time limit ended the family intake build before a closing summary, and the form dropped every photo a parent picked, so the two-photo rule blocked every submission.

Built a Dota 2 match tracker that saved a logged match, labeled its demo matches and kept them out of the stats, and added the heroes page when asked.

With thinking off, it built the family intake form in 6 minutes 14 seconds so it saved every answer and both photos, and it removed its own test row when it finished.

With max thinking, the test time limit ended the build, and the follow-up message finished a form that saved every answer and both photos, with every sample family labeled.

Built the Dota 2 match tracker with both settings, and both saved a logged match. With max thinking it labeled its sample matches. With thinking off it had already built a ranked heroes tab, so the follow-up change made no edit and said so.

With thinking off, the form uploaded both photos, but the save was rejected, and the teacher page showed its sample families with blank names.

With thinking on, the form sent each submission to an address that does not exist, and the teacher page showed families typed into the page instead of saved ones.