3 ms·

> Right now there are still no navigation library. React Navigation and React Native Navigation are both viable options with their own pros and cons. Been usin

> Right now there are still no navigation library. React Navigation and React Native Navigation are both viable options with their own pros and cons. Been using them successfully in different projects. https://reactnavigation.org https://reactnavigation.org https://wix.github.io/react-native-navigation https://wix.github.io/react-native-navigation

filleduchaos 8y ago
I think what they meant is that there is no built-in production-ready navigation library, which is honestly atrocious.
- k__ 8y ago
  I never understood the obsession with native navigation libaries. I built a bunch of apps with JS navs and nobody ever complained...
  - mwcampbell 8y ago
    Did you test your app with VoiceOver, the iOS screen reader for blind people? The difference between non-native and native navigation is particularly noticeable in that case, unless perhaps you fire a UIAccessibilityScreenChangedNotification after navigating to a new screen. That's just the scenario I'm aware of. I haven't done any real projects with React Native, so there may be other pitfalls.
    - LeoNatan25 8y ago
      Of course not. They are a lazy developer that care little about the user experience.
      - mwcampbell 8y ago
        As passionate as I am about accessibility, I try not to use an accusing tone. There's no way we can know the state of mind, priorities, and constraints of the developer in question. Even large companies don't have unlimited resources. So we can't fault developers for looking for ways to do more with less. We just need to do what we can to make sure developers are informed about the pitfalls, and plead with them to consider important user experience factors like accessibility.
  - filleduchaos 8y ago
    "Built-in" and "native" don't mean the same thing last time I checked.
    - morenoh149 8y ago
      I think you mean 'built-in' into react native? Facebook routinely lets the community settle on the correct api aside from a limited core. E.g. react router on web has gone through many versions and there are several community libraries for doing web navigation and how you want to track that application state.
      - filleduchaos 8y ago
        And as a result there's a ton of churn, waiting for third parties to update their libraries (sometimes forever) and beginners having to make choices on how to do the most basic things without the experience or knowledge to help them make good decisions.
        morenoh149 8y ago
        It's just beyond the needs of fb and what they cared to provide for. No one is paying for the extra dev work, so until some other entity pays or volunteers that will be the situation. Incidentally, Expo did extend RN to cover many of the missing APIs. It's just the reality we live in.

filleduchaos 8y ago

I think what they meant is that there is no built-in production-ready navigation library, which is honestly atrocious.

k__ 8y ago
I never understood the obsession with native navigation libaries. I built a bunch of apps with JS navs and nobody ever complained...
- mwcampbell 8y ago
  Did you test your app with VoiceOver, the iOS screen reader for blind people? The difference between non-native and native navigation is particularly noticeable in that case, unless perhaps you fire a UIAccessibilityScreenChangedNotification after navigating to a new screen. That's just the scenario I'm aware of. I haven't done any real projects with React Native, so there may be other pitfalls.
  - LeoNatan25 8y ago
    Of course not. They are a lazy developer that care little about the user experience.
    - mwcampbell 8y ago
      As passionate as I am about accessibility, I try not to use an accusing tone. There's no way we can know the state of mind, priorities, and constraints of the developer in question. Even large companies don't have unlimited resources. So we can't fault developers for looking for ways to do more with less. We just need to do what we can to make sure developers are informed about the pitfalls, and plead with them to consider important user experience factors like accessibility.
- filleduchaos 8y ago
  "Built-in" and "native" don't mean the same thing last time I checked.
  - morenoh149 8y ago
    I think you mean 'built-in' into react native? Facebook routinely lets the community settle on the correct api aside from a limited core. E.g. react router on web has gone through many versions and there are several community libraries for doing web navigation and how you want to track that application state.
    - filleduchaos 8y ago
      And as a result there's a ton of churn, waiting for third parties to update their libraries (sometimes forever) and beginners having to make choices on how to do the most basic things without the experience or knowledge to help them make good decisions.
      - morenoh149 8y ago
        It's just beyond the needs of fb and what they cared to provide for. No one is paying for the extra dev work, so until some other entity pays or volunteers that will be the situation. Incidentally, Expo did extend RN to cover many of the missing APIs. It's just the reality we live in.