Skip to content
This repository was archived by the owner on Oct 27, 2021. It is now read-only.
This repository was archived by the owner on Oct 27, 2021. It is now read-only.

RRN future #54

Open
Open
@LeoLeBras

Description

@LeoLeBras

Hi everyone!

It’s been a very long time since I’ve been active on this repo. I’ve been really (really really) busy this whole year. I offer my humblest apologies for the unanswered issues and all your great PRs that have not been reviewed yet. But everything will be back to normal really soon, I promise.

I take this opportunity to share with you my thoughts about the future of the library, and especially the long-awaited v2. I don't want to give you any ETA yet, but be ready to get your hands on the alpha rather sooner than later! As a matter of fact, this matches with some technical needs inside my company, so you can expect a sustained development over the next few months.

Initially, this library wasn't meant to bring anything completely groundbreaking. It only allows you to combine the best of react-router@v4 - that offers an incredible API - with react-navigation, another library which offers lots of components for mobile app navigation.

One of the major problems of react-router-navigation is that it was initially developed as an experiment and I decided to publish it without thinking that it could exceed these 200 stars. So: my deepest apologises for never really taking the time to think about the evolution of this library. But this should end now. The upcoming v2 should allow a more user-friendly usage and cover a wider range of applications, without changing its API.

The main points of this new version are:

  • Documentation. Recurring questions have been asked about simple use cases of this library. I'm looking for some charitable souls to make up for this lack. A well-documented project is important to create a strong community and develop a library that is always accessible. Hit me up if you’re interested! 🙂
  • I also want to set up more tests to improve stability and robustness and isolate the different modules, including the library logic. This would ensure that any update of react-native or react-navigation would not endanger the proper functioning of the library. It should doable through simple unit tests with Jest, and E2E tests with Detox.
  • Add a <Modal /> component and a <Drawer /> component.
  • I also want to implement native navigation with react-native-navigation. This feature is part of an internal need at my company, that I would like to share with many people as possible. If some of you are interested, chime in! We have some great things to do together.

A stable v1 should be available in a few months. There are still a few issues to fix and updates of react-native, flow and react-navigation to operate.

I now give you the stage so that you can tell me your desires for this v2, just to be sure I haven't forget anything. I'm also interested in knowing how you use the library on a daily basis. Do you use it on iOS? Android? In production? In which company ? This will allow me to better understand how you use this library in order to guide its development towards the best possible path.

Stay tuned! 😊

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions