WhoBuilt

Rapid React Native

Sep 14, 2018· 25 min· 169 views·Watch on YouTube

Speaker

Gant Laborde of Infinite Red talks about speeding up React Native development with Ignite at a Callstack event.

Mobile development’s changing costs

Laborde describes how mobile development once meant separate iOS and Android work, long compile waits, and costly platform expertise. He says React Native offered web developers a way to build for mobile across platforms, but earlier approaches such as RubyMotion did not support Android well enough for his team.

Ignite as a practical starting point

Laborde says JavaScript’s many competing opinions can make it hard for newcomers to choose tools and practices. Infinite Red created Ignite as a React Native starter with conventions, plugins, documentation, and support for Android, iOS, and Windows.

Building a small app live

Laborde uses Ignite to recreate Textables, an ASCII art app with more than 26,000 downloads that sells for a dollar. He generates a screen and grid, connects the app to existing data, and adds a text input and clipboard action. The live demo includes a few debugging detours, illustrating the hands-on workflow.

Customizing tools and debugging

Laborde explains that teams can change Ignite templates for a project, fork them, or create plugins, so they do not have to keep the starter’s defaults. He also shows Reactotron displaying app actions, state, and API responses without remote JavaScript debugging, and describes snapshots for moving between states.

Community and adoption

Laborde says Ignite’s plugin system can work with other boilerplates, including one built around NativeBase. He cites a community of more than 1,200 people, over 6,000 GitHub stars, and the Chain React conference app as examples of adoption. He asks users to share what they build so the team can learn how Ignite is used.

Takeaways

  • A starter kit can give a team a working baseline for tools and conventions.
  • Keep generated templates editable so project-specific needs can shape future code.
  • Show new developers concrete examples that go beyond a bare Hello World screen.
  • Use tools that expose app state and API activity during development.
  • Ask users to share what they build to learn whether open-source tooling is useful.

Mentioned in this talk

Search inside this talk

What was claimed 11

Show all 11 facts

Related talks