Thoughts on Million.js?
I am considering how to move forward with the web version of my application. I am currently using react native for the mobile version of the app, and the web version is just very janky because the app is only developed for web right now. The switch to web will require big changes in UI, and the entire UX could change due to the nature of phones or an IPAD vs a keyboard and mouse and a larger screen. So I thought it might be good just to build a new app using react.js instead of react native, re-using lots of the code to query the backend, and while I'm at it, also use million.js. The application is somewhat data heavy, basically an analytics dashboard for safety reporting, with the mobile version good for employees to make reports. The mobile version should IMO be more geared towards that with basic analytics, with the web version geared towards Admins, with richer dashboards and functionality. So, my question is, are there any downsides for a relatively greenfield web app to use million and react.js? The backend is in AWS
9 Replies
Million is just a patching for the bigger react issue
If you know that the page will have lots of contents and very interactivity
You can try your luck with million, or try something like svelte/solidjs
I only have 3 weeks left in my internship so my fear is that if I choose a new framework like svelte I wouldn't be able to reuse much from the react native project. So that's why I'm interested in million vs vanilla react
If it improves the page then great? If not then don’t use it 🤷 it doesn’t loon like a whole lot of work to add it to anything
million seems like the use case when you know you need the perf
not as a first thought
Okay. So might as well just forego it and then use it if perf is a problem. I have a feeling it might be a problem for the analytics page, but ofc we'll see. Thanks for the thoughts
Analytics can be offloaded to party time
Which is a great concept, but not just there. A lot of analytic issues will pop up when you will do that @lopen3
Maintaining multiple client which share a lot of code should at the very least be done with a monorepo imo. If you don't want to share the UI then take a look at t3-turbo, if you do want to share the UI take a look at t4 stack 🙂
I would also recommend taking a look at legend-state which solves a similar issue to million.js from another point of view (from the state management side)
I'm doing platform checks for web vs mobile and keeping everything in react native for now. My internship is basically done so no need to worry about it anymore lol