![Cover image for [Discussion] Challenges in Frontend for SaaS Apps.](https://res.cloudinary.com/practicaldev/image/fetch/s--2yrMNhfo--/c_imagga_scale,f_auto,fl_progressive,h_420,q_auto,w_1000/https://thumbs.dreamstime.com/b/white-paper-background-text-technical-discussion-192375177.jpg)
Dealing with SaaS apps requires some specific considerations on the frontend. Some might be related to the tools, architecture, or libraries on the whole FE stack.
- What challenges did you face?
- How you fixed those challenges?
- Which area do you think is underdeveloped?
I would love to share and expand my experience in this field as a series "Frontend for SaaS Apps Series" and your points will help me define the right scope and starting point.
Top comments (1)
One of the things we faced, is that we have a SaaS with certain workflows but those workflows might vary between customers and adding a lot of if statements will make the code really ugly.
Our solution was to introduce "Flavoring" by replacing React components on the transpile time "Babel". And this forced us to write better reusable and smaller components.