WhoBuilt

Building Components Visually Using Draftbit

Oct 8, 2019· 22 min· 1.8K views·Watch on YouTube

Speaker

Peter Piekarczyk, co-founder of Draftbit, presents at React Native EU 2019 in Poland on building mobile apps visually and exporting React Native code.

A new interface for app development

Piekarczyk traces a shift from assembly and punch cards to web languages, IDEs, and frameworks that made software easier to build. He argues that visual tools can extend that accessibility to app development, while giving engineers more time for complex work.

Draftbit’s workflow and design system

Piekarczyk introduces Draftbit as a visual app builder shaped by his team’s experience iterating on Orchard, a networking app built with Expo, GraphQL, and React Navigation. Users can arrange components, preview changes on connected devices, and export the source code. Draftbit’s Jigsaw system supports reusable colors, fonts, spacing, shadows, and typography.

Reusable screens and navigation

Draftbit offers templates for common screens such as sign-in and profiles, so teams can reuse those instead of rebuilding them. Its visual navigation editor supports tab icons, colors, stacks, and onboarding routes, then generates an app navigator file. Users can also save a layout as a reusable component for use across screens and apps.

Connecting app data

Piekarczyk describes configuring requests by entering a URL and method, previewing the response, and mapping data fields to components. He also demonstrates a GraphQL Explorer that generates queries from selected schema fields and connects them to app components. He names OneGraph, Amplify, and Hasura as compatible endpoints.

Planned improvements and a starter app

Piekarczyk says the team is working on a better configuration panel, keyboard shortcuts, and making accessibility easier to address early. Planned screen-building presets would arrange components automatically. He also presents Rentpit, an Airbnb-style starter app that users can preview, copy, customize, and export.

Takeaways

  • Prototype screens visually and preview them on devices before exporting the code.
  • Use shared design tokens and reusable screen templates to speed up iteration.
  • Treat navigation and common flows as reusable parts of the app.
  • Preview API responses and map fields to components before wiring up screens.
  • Build accessibility into the design workflow early.

Mentioned in this talk

Search inside this talk

What was claimed 14

Show all 14 facts

Related talks