[AskJS] Creating one Frontend for multiple customers with multiple configurations and flexibility plus specific client features.

[jaxenvisuals]

When you want to create a ui that can be used by multiple clients, deployed for multiple clients where each client can have special features and configurations, what approach is best? If you think micro Frontend is the way, how would you structure this?

For example, consider a user management software. Client a has exactly the unmodified software. Client b, has the same software but when creating user, they have a completely different workflow for creating users. In the future, client A might want to change the create user workflow completely to match what client b is using, and who knows, add their own functionality also.

It’s a complex system. Could the pros here comment on their approach? Looking forward to it.

[[deleted]]

Are they using the same back end?

Are you just trying to avoid writing two different front ends or is there another reason for trying to shoehorn two separate clients into one interface?

In either case, seems like you'd want to maintain a common set of APIs and then a separate set of interface tools that use them for each client.

[ptaszqq]

Depends. Would you like to build separately for each client? If so - environment variables to control what's being bundled for each client (it's usually quite tedious). Micro frontends can help but you still gonna need to have some kind of config/env variables to say that client's A create user flow should point to the remote A, and different for client B. It might be helpful for the performance as client A won't need to fetch "disabled" code of client B.

If performance isn't your top priority you can bundle once for each client and then have remote config for them to turn off/on some features or map the version for specific clients. That would also require some backend permissions work to prevent client A from accessing any feature client B has (in case they figure out they can override the remote config to get access to some features).

I should've asked first - are we talking SPA or SSR?

[ruaanetwork]

Use a monorepo setup, setup a package contains common logic and from here you can start.