shards-react VS react-admin

Ca sa fiu mai specific, chestii de genul: https://designrevision.com/downloads/shards-react/

Links: Demo | GitHub repo | npm page

16. Shards React

I was learning React JS front end and in this journey of self learning, I have achieved many milestone like utilizing react-admin framework. I also implemented two-factor authentication using Authenticator tools with react-admin framework. It was a very challenging job to include two-factor alongside react-admin authentication as there is no tutorial available for it. But this is very much required in the era of AI infused cyber threats to secure your applications.

React Admin

With a simple relational data model, developers can easily modify the system to store additional data. Its component-based architecture allows for replacing or customizing any part of the application, giving developers full control over the user experience. Built using React and react-admin, two widely supported frameworks, it comes with a rich library of pre-built components ready for use.

Whenever I see the word "framework", I can't help but think of the Linebreakers' song "We're Gonna Build a Framework". That aside, React-admin has over 25,000 users around the world. It's a single-page application framework, allowing you to build web apps running on top of REST/GraphQL APIs, using TypeScript, React and Material Design. React-admin's latest update brings refined lists and forms, dependency update, and easier application initialisation.

> "Are there examples of companies adopting this model?"

Many examples across the industry:

- Autodesk AutoCAD (closed) + Plugins/Addons (many open)

- MS Windows (closed) + Many 3rd party programs (open)

- Github (closed) + Github Actions (open)

- Npm (closed) + Npm modules (mostly open)

> "What are the potential benefits or pitfalls?"

Benefits:

- Harder to replicate, the company gets to keep the "secret sauce" a secret

- Opening up a way to "extend" the platform means 3rd party developers add value to your system

- The core isn't open, so less effort is required to maintain compare to OpenSource

Pitfalls:

- Closed-source is hard to verify, company is essentially saying "trust me bro"

- Less innovation, as user's can't contribute to the core

> "How does it impact community engagement and software adoption?"

There's hardcore FOSS advocates that will hate anything not fully open. But a business has to make money and protect it's IP, having a "closed core" is one way to do that and ensure a sustainable business model.

Another approach is the opposite, open-core + closed-premium-addons. An example of this is "React Admin"

- Open Core -> https://github.com/marmelab/react-admin

- Premium Modules Offering -> https://react-admin-ee.marmelab.com/

Official Website: https://marmelab.com/react-admin/

React-Admin is a React-based frontend framework for building admin applications that talk to a backend data API. It offers a pluggable mechanism for easily adapting to the specific API style of your backend.

With these features, data fetching and forms become significantly easier to implement in React. However, creating a great user experience involves integrating all these hooks, which can be complex. Alternatively, you can use a framework like react-admin where user-friendly forms with optimistic updates are built-in.

31.react-admin

For the admin panel, or basically anything with basic crud operations, take a look at https://marmelab.com/react-admin/. Most frontend devs don't like it, since it limits you somewhat in customization, but at the same time, it is very easy to grasp for someone coming from a backend dev profile, who just wants a crud UI. It even has a guesser template that proposes an initial screen layout based on the response of your api, which you can then copy-paste and finetune. It is really made to make quick admin crud ui's.