uclusion_web_ui VS spectrum

It's been a long road getting Uclusion's UI right and it's still changing as we get more feedback. We're also finding this level of polish in React to be very challenging - see https://github.com/Uclusion/uclusion_web_ui if you are interested in the underlying code.

Both my co-founder and I transitioned from backend to full stack in order to be able to contribute to https://github.com/Uclusion/uclusion_web_ui What we learned is that the best way to learn front end is by doing. And this is confirmed by the fact that twice now front end people that wanted more experience in React or Material UI (cause every Javascript library is its own universe) have contributed to that repo for free.

You can check out https://github.com/Uclusion/uclusion_web_ui to see some of our struggles. I'd say:

Not made for practice but this is production code you can look at https://github.com/Uclusion/uclusion_web_ui

Confused what you mean by context shouldn't be used for frequently updated variables. How frequently? We are using context for exactly your use case https://github.com/Uclusion/uclusion_web_ui/tree/master/src/contexts all over and it works great - especially in conjunction with AWS Amplify message bus.

Some people who wanted to better learn UI just volunteered to help me with https://github.com/Uclusion/uclusion_web_ui for free. I'm not saying you should do that (they were past code camp kind of level) but their idea to volunteer for projects to improve their UI skills seems valid.

See the original code here. In my case I also have a fancy ScrollContext to scroll to the id but if you are only trying to get to the tab you don't need that.

You can use promises and Promise.all to load all of this data instead of looping through an array. Or you can chain the promises so they run sequentially if you want to avoid making all the network calls at once. See usage of globalFetchPromiseChain in https://github.com/Uclusion/uclusion_web_ui/blob/master/src/api/versionedFetchUtils.js

In order to help with the learning curve in React, Uclusion uclusion_web_ui is now public with a Readme to many articles on Dev.To explaining its code.

For a good reference repository, you should check out Spectrum’s GitHub repo. It’s organized well, uses good practices, and given that it is the entire Spectrum product, can provide a lot of system design and architecture insight.

You have now started on your first React Native app in Expo. This is the same tool which is used for creating apps like Facebook, Instagram, Coinbase, shopify, Tesla, Uber Eats and many more. You can read more on Expo here: https://docs.expo.dev/ or check out an open source app here: https://github.com/withspectrum/spectrum and checkout an enterprise boilerplate here: https://github.com/infinitered/ignite

GraphCDN passes subscriptions through to your origin, so they keep working just as they did before! I personally used GraphQL subscriptions with relative success at Spectrum and I'm very excited about live queries nowadays.

We were using Slate at Spectrum[0] back in 2017/2018, eventually switched to DraftJS due to cross-browser issues but that was honestly equally frustrating to use and support across many browsers.

In hindsight, we should've just had a GitHub-style markdown editor: https://mxstbr.com/thoughts/tech-choice-regrets-at-spectrum

It sounds like the situation has improved since then! I'll definitely try Tiptap if I ever need to build another RTE.

[0]: https://github.com/withspectrum/spectrum

Checkout spectrum

I was lucky enough that I somehow stumbled upon withspectrum/spectrum repo and found out that there actually are great applications running on the internet, under load and are dutifully maintained while being open-source! Spectrum has been back then one of the most eye-opening experiences for me as a junior developer. Although I didn't actually ever got to build a system like that, it taught me a great deal on how such app operates and how can various libraries be used.

Special thanks to the Spectrum Project (Here) for laying the foundations to Bulletproof Express. Also, many thanks to Node.js Best Practices (Here) and Bulletproof React (Here) for providing guidance on how Enterprise-Level Software should be written.

During last few years i managed to stumble upon a few repositories with large apps that have been a great learning source and an inspiration (such as https://github.com/withspectrum/spectrum) but these are few and far apart.