~/talk

When to Go Native Over Javascript

Talkat Chain React 2017 · on Tuesday, 2017-07-11· [react-native]
slides:none on file

Demonstrates concrete tradeoffs: Expo requires detaching to add native modules, CodePush cannot change native binaries so a new release is needed, and a navigation experiment shows native navigation renders fewer offscreen views and reduces memory compared with JS stacks. Builds a delivery app that proves periodic geolocation needs platform APIs so background location requires enabling iOS background modes and native timers. Code and example apps are on Github and the native parts work as shown.

AI-written summary · about

  1. 0:00Start
  2. 2:52What is Expo?
  3. 3:48How does Native Code affect expo?
  4. 5:05What is CodePush?
  5. 8:05Example App
  6. 10:21React Native Navigation
  7. 11:39Accessibility
  8. 13:19React Navigation
  9. 13:43Native Libraries Cons
  10. 15:15What does the Driver app do?
  11. 17:19Demo Source
  12. 18:16Testing
  13. 20:28iOS Background Modes
  14. 22:06Things To Note
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.