I am an intermediate react dev – the only front end dev – at a small B2B company in a small industry with products related to inventory management. I’m about to release our first react app and will begin real work on our second soon. The two apps will be very closely related; in a nutshell one allows customers to view details and reports about their inventory, while the other allows customers to not only view the same type of data but to interact with their inventory (make adjustments, transfer material, and so on).
The two apps will share a lot of basic functionality, but will have plenty that is different. Each app will have pages to view the same inventory and reports, but there will be different options and buttons within those pages. There will be some whole pages that will be in one app, but not the other. I am trying to determine the best way to handle the duplicated functionality while separating our different pages/components/settings/etc.
My current plan has been to put build environment variables all over the place to determine what gets built into each app – which pages, which routes, which components within a page.
The other obvious option is to just have two fully independent apps, and manage the shared functions manually.
As the only front end dev my main concern is simplicity, and I’m actually starting to lean toward having two completely separate apps and dealing with copying functionality back and forth manually. But no matter which way I look at this with the future in mind, it feels daunting! Mostly I think this post is just to help me organize my own thoughts, but I’m curious for any experiences or advice related to a situation like this.