OK but thats simply doesn't perform. You can't say "only rendering what is visible should be handled by the browser" and call that a solution unless you have a magic wand to make Chrome/other browsers do this. The…
> I feel like virtualization is not the right way to handle things. How would you handle it?
Optimizing for the P95/99 case of performance typically makes everything better as a whole.
Our core team - and indeed our original team - were native developers not React JS ones. We chose React Native because it was a pragmatic choice and the best tool for our situation. As our startup gained traction and we…
Thank you for the kind words!
The strongest RN teams and engineers I've seen tend to be those that either already have or are willing to acquire knowledge about how native app development works under the hood. It greatly augments your ability to…
Thanks for the read, and the support!
Blog author here. As a native app developer, I would say that the trade off is similar to developing an app on native Android vs. native iOS. You inevitably must solve problems on Android that iOS has not yet solved (or…
Well it’s been three years so far - we shall see :P I know this comment is a joke but in all seriousness even if we did move away I think it would still mean we got several years of great utility out of the framework.…
Based on our experience yes I would certainly consider doing the Android side in React Native starting today. While the performance footprint is mostly the same - the ecosystem and feature set around it has improved a…
Thank you! :)
It's been discussed a lot internally - I would love to gift Nitro to folks myself ala Reddit Gold :) I believe it's something we may eventually take on - just not currently planned - there are a lot of ways we could…
It's a valid point :) that probably wasn't the best example - although it would likely be quite a journey to somehow ship the forked support library. Native iOS would have been a better example as that code is not open…
Thats really cool :D I think getting it to the point where it's not just occasionally synced is really helpful for upstreaming contributions and bug fixes.
It's not about cost, it's about impact. The team - myself included - works normal eight hour days and there is no "crunch time" (other than very rarely when we have external dependencies like when we launched our…
We are actually starting work on allowing pasting images from the clipboard this week :D So stay tuned! Thanks for the kind words, the team really appreciates it.
The iOS application can safely pull data and perform actions from just about every Store (we don't use redux but the idea is the same https://redux.js.org/api-reference/store) and Action Handler…
* Mentioned in another comment, but generally the performance of animations was poor with mixed in with any other kind of UI rendering - particularly on older phones (when we prototyped iOS we really only focused on the…
I'd suggest reaching out to our CX team (support@discordapp.com) - we really do care and you will get a reply :) I'm not an expect on voice but iirc we do use a different codec than Skype so the audio is not going to be…
It's less that it's bad (in my opinion) and more that on Android you have a much wider range of hardware to support ranging from quite new and recent, to basically ancient almost flip phone level. I am hoping that in…
The core Android team is four engineers so about double in size. This makes some sense since on Android we have to re-write most of the stores/business logic and not just UI. We have modeled the architecture similarly…
Hi all, Discord engineer here! If anyone has any questions about the post or our experience using React/React Native the team would be happy to answer them!
OK but thats simply doesn't perform. You can't say "only rendering what is visible should be handled by the browser" and call that a solution unless you have a magic wand to make Chrome/other browsers do this. The…
> I feel like virtualization is not the right way to handle things. How would you handle it?
Optimizing for the P95/99 case of performance typically makes everything better as a whole.
Our core team - and indeed our original team - were native developers not React JS ones. We chose React Native because it was a pragmatic choice and the best tool for our situation. As our startup gained traction and we…
Thank you for the kind words!
The strongest RN teams and engineers I've seen tend to be those that either already have or are willing to acquire knowledge about how native app development works under the hood. It greatly augments your ability to…
Thanks for the read, and the support!
Blog author here. As a native app developer, I would say that the trade off is similar to developing an app on native Android vs. native iOS. You inevitably must solve problems on Android that iOS has not yet solved (or…
Well it’s been three years so far - we shall see :P I know this comment is a joke but in all seriousness even if we did move away I think it would still mean we got several years of great utility out of the framework.…
Based on our experience yes I would certainly consider doing the Android side in React Native starting today. While the performance footprint is mostly the same - the ecosystem and feature set around it has improved a…
Thank you! :)
It's been discussed a lot internally - I would love to gift Nitro to folks myself ala Reddit Gold :) I believe it's something we may eventually take on - just not currently planned - there are a lot of ways we could…
It's a valid point :) that probably wasn't the best example - although it would likely be quite a journey to somehow ship the forked support library. Native iOS would have been a better example as that code is not open…
Thats really cool :D I think getting it to the point where it's not just occasionally synced is really helpful for upstreaming contributions and bug fixes.
It's not about cost, it's about impact. The team - myself included - works normal eight hour days and there is no "crunch time" (other than very rarely when we have external dependencies like when we launched our…
We are actually starting work on allowing pasting images from the clipboard this week :D So stay tuned! Thanks for the kind words, the team really appreciates it.
The iOS application can safely pull data and perform actions from just about every Store (we don't use redux but the idea is the same https://redux.js.org/api-reference/store) and Action Handler…
* Mentioned in another comment, but generally the performance of animations was poor with mixed in with any other kind of UI rendering - particularly on older phones (when we prototyped iOS we really only focused on the…
I'd suggest reaching out to our CX team (support@discordapp.com) - we really do care and you will get a reply :) I'm not an expect on voice but iirc we do use a different codec than Skype so the audio is not going to be…
It's less that it's bad (in my opinion) and more that on Android you have a much wider range of hardware to support ranging from quite new and recent, to basically ancient almost flip phone level. I am hoping that in…
The core Android team is four engineers so about double in size. This makes some sense since on Android we have to re-write most of the stores/business logic and not just UI. We have modeled the architecture similarly…
Hi all, Discord engineer here! If anyone has any questions about the post or our experience using React/React Native the team would be happy to answer them!