Support for react-native-screen 's createNativeStackNavigator

[hirbod]

Hi,

would be awesome if this lib would support

import createNativeStackNavigator from 'react-native-screens/native-stack';

since the performance of native-stack is awesome and absolutely no comparison to the usual createStackNavigator

[hirbod]

@IjzerenHein thank you very much, these are good news!

[hirbod]

@IjzerenHein any news on the progress?

[IjzerenHein]

Status update (as I send to a stakeholder by email)

I have not not been able to work on it this month. I injured my back earlier in Januari, but luckily everyone is fine again. And at the moment I am putting all my time into reaching a deadline for a client, and another client also requires attention for their app launch.

The current status is that the JS part is about finished in terms of functionality. I still need to create PRs in react-navigation to make some changes there. As for performance and timing. That is the biggest problem. I've sped up the time it requires react-navigation-shared-element to trigger the transition, in order to have a smooth transition, but that has revealed new problems. For some reason, the layout measurement is incorrect when snapshotting the views earlier. I'm pretty sure it has something to do with how RN does layouting or something with react-native-screens, but that requires further investigating and deeper probing. It's a tough problem for which I really need to dedicate some time to understand (and hopefully fix).

[hirbod]

@IjzerenHein it's been 6 months now. Do you really think that's ok how you treat your sponsors? You can't accuse us of being impatient or not understanding your situation, but now I've reached the point where I feel really screwed.

I have brought the whole thing with haibert to work and it comes absolutely nothing more from you.

I'll wait until the end of the month, otherwise I expect a refund. Exactly this kind of stuff is the reason for people developing trust issues and being extremely careful funding projects or developers.

[MauriceNino]

@hirbod I don't think you understand what a donation is. You willingly supported an open source creator for a library that he has already put great efforts in to, in the hopes that he is then motivated to implement a feature you would like to see. But that is not how Open Source works. You did not pay for a product, and you are not entitled to any return on that money.

If you absolutely need this feature, create it. Fork the library and create your own version, or create a pull request and add the features you want.

If @IjzerenHein gives you a refund or not is his decision, but I would definitely not. He is putting his clients (who probably paid for a certain performance/product) and his health first, and an open source project second. I don't think there is anything wrong with that.

[hirbod]

@MauriceNino I did not make a donation, I funded for this specific feature. I am not using this library, because it has this missing piece. I also came up with the idea to collect this funds FOR THIS SPECIFIC feature. Not more, not less. Do your research until you try to tell me how kickstarting/funding works.

I am sponsoring PLENTY open source projects. I am donating couple of hundreds every month on open source projects (I am changing them every month to show my appreciation to libs I am using on a regular basis). This is something totally different and I would never do a call out on them to have anything specific developed, just asking for what they have offered through github sponsor tiers.

This one is different, since I am not using it and I wanted to kickstart this specific feature. But the project progress has been stuck for couple of months now.

[MauriceNino]

@hirbod Still, you donated (or funded, you can call it however you want...) to a progress, not a product. What if the goal is unachievable? What if it would take way too much time? You can't just pay a fixed sum of money and expect that whatever you want will be done. Sure the author may have communicated it better, but he is not obligated to complete a feature for you, unless you set up a legal contract with him (and on the moral side: pay him a fixed hourly rate).

There is also no GitHub Sponsors tier that says "You earn the right to get a feature in a set amount of time". Do your own research before telling me how to do mine.

Also, I don't give a damn what you donate to other projects and I also don't care if you use this library or not? Bringing up how generous you are doesn't prove your point, nor add anything to your argument.

[mrousavy]

I don't want to take any side in this argument here, but also note that Hein is a very good developer and $200 pays for about 1 or 2 hours of development in this business. That's not a lot of time, we can't expect a car to be built for $200 either.

[hirbod]

@mrousavy I am not saying it is much. But the whole campaign gathered 2k, thats a decent amount for a feature imho. I am just speaking for myself, that I did not donate money, I funded for something. Thus I except some transparency and some ETAs. Its been more than 6 months now. I would rather donate that 200 bucks to an Ukrainian fund (which I also already did)

[MauriceNino]

@hirbod It is a decent amount, I'm not saying it isn't - I am just trying to tell you that you are not obligated to get anything for your money. It doesn't matter if you think it is a donation, or not.

If you think you have been wronged, try talking to GitHub about it, but I am pretty sure they will tell you more or less the same thing.

Also, please stop bringing up all your other donations, the humblebragging is just weird.

[hirbod]

@MauriceNino

Still, you donated (or funded, you can call it however you want...) to a progress, not a product.

It is a big difference if you donate or fund something.

What if the goal is unachievable?

If a goal is unachievable, then just be transparent and we can move on. I also lost money and time on kickstarter. This is basically the same: you fund for something with risks, but at least get some insights, ETAs etc. There has not been much traction on this project lately anyway. It feels like it has been frozen.

There is also no GitHub Sponsors tier that says "You earn the right to get a feature in a set amount of time"

The tiers are promises the developers make by themselves. Some do not have any, some have. I was referring to those who do pledge what you can except from a tier. This one was funded trough PayPal Moneypool anyway.

Also, I don't give a damn what you donate to other projects and I also don't care if you use this library or not? Bringing up how generous you are doesn't prove your point, nor add anything to your argument.

It is a big difference if I use this library or not. If I was a regular user of this software, I would've been quiet on the whole topic, since I have use for it and would count this in as a donation. But in its current form, it might be helpful for others, but not for me, because I am only using the native stack.

The whole reason I started this argument with you was not to prove how generous I am (which I am), but to prove that I know the difference between a donation and a funding and that I do have a lot of respect for open source software developers and I do my best to give something back. I am done arguing with you.

P.S: Don't tell me what to talk about and not and mind your own business.

[brentvatne]

i know @IjzerenHein personally and can vouch that if he had the time to work on this then he would.

it's important to have empathy and recognize that sometimes things don't go to plan. i understand that some folks are very interested in this feature, but please remember that we are all humans here trying to do what we think is best. feel free to reach out to me if you have any concerns.

[davesimtech]

As far as I'm aware the moneypool stated it would be used towards the development of the feature, however it was no guarantee that it could actually be achieved. I donated (although a rather small amount) fully aware of that situation with the hope it could be achieved and more out of support for the library and all of work @IjzerenHein has done, as it was described on the moneypool.

@IjzerenHein I know sometimes explaining what needs to be done actually takes more effort than actually doing the implementation. However, is there anything that we can do to help, any pointers for things I can look at?

[jkk]

My company donated -- no hard feelings from us. "No guarantees" was literally in the moneypool description. We actually considered doing a small up-front donation, no strings attached, and another larger donation contingent upon completion, for that exact reason. But we didn't do that, so no expectations were violated. We appreciate all the work done so far!

[IjzerenHein]

Dear fellow coders,

All good things come to an end. And I have decided to stop working on shared-element as it no longer fits into my life and I lack sufficient time, energy and motivation.

One of the most important reasons for that is that I haven't used shared-element myself in the last 2 years. And maintaining Open Source libs is something you do mostly because of the love and utility you have for it yourself. As I've grown older the energy to spend time on my OS libs (either in my spare time or between projects) has decreased, to the point that I get very little satisfaction from it. I'm content with how the native building blocks turned out and it's an interesting solution to a rather tricky problem. The react-navigation binding has however been a struggle from the start. When ReactNavigation@4 support was completed, ReactNavigation@5 was released, and in the beginning things were still changing and breaking at a regular pace. Supporting, testing and making sure the code-base is maintainable requires a far greater dedication than I am willing to put into it, for something I don't use myself.

Looking back I should probably not have accepted the donations/funds to work on this project/feature. But it felt like such great energy and love for the project that I wanted to give it a go. Circumstances have however not been favourable and breaking up with my GF, moving to a new place and being an emotional wreck at times have not helped. Some good progress has however been made but it's not there yet. The testing app has been extended to showcase all the tests with the native navigator. The whole lifecycle mechanism has been reworked to capture the start of the navigation faster. Temporary patches have been applied to react-navigation to fix certain issues. The current state is that it somewhat works, but there is an issue with determining the position of the target element. Which seems somehow related to the native code performing its measurement sooner in combination with react-native-screens. This requires deeper analysis and debugging in order to understand the problem and hopefully fix it.

Which brings me to this last paragraph. I would love to see that shared-element continues to exist, as it solves a problem within the react-native ecosystem. Functionally it's probably not essential, but it's one of those things that brings shine to an app, and takes the attention of the user on a journey to make for a better UI experience. I'm therefore looking for a new home or maintainer for both react-native-shared-element and react-navigation-shared-element. And I will make $1000 of the donation funds available to the person or company willing to take this on (and continue with native-stack support). Please reach out to me personally if you want to take this over or have ideas or suggestions for a new home.

peace out, Hein

[haibert]

@IjzerenHein

Really sorry to hear about your recent struggles. You did your best. Thank you for the progress that you did provide and over all mental health and life balance is more important than anything else, and Im glad you chose a path that will give you more of that. Wish you the best Hein!

[Johan-dutoit]

All the best to you @IjzerenHein! Mental health trumps everything.

Is this something the react-navigation team or SWM team could bring into their space? Totally get it's a hard ask and both do so much to help the RN community already!

cc @satya164 & @kmagiera

[nandorojo]

@IjzerenHein - wishing you the best. The open source path can be tough. Thanks for everything you contributed. I hope someone else is able to continue your great work.

[hirbod]

@IjzerenHein thanks for the statement and honesty. Through your open statement I have of course full understanding for the process and your situation. I wish you all the best for the future.

[fukemy]

@andreialecu pay 10000$ for this help

[andreialecu]

I'm not sure what that's supposed to mean, but there's a draft PR here that is supposed to implement this into react-native-screens so if you have any bounties to throw, perhaps throw them over here: https://github.com/software-mansion/react-native-screens/pull/1479

[RajeshChoudhary1700]

![Uploading _fed1d2ff-2157-46aa-b3fb-ec5f465f3594.jpeg…]()