FSD Architecture for Web Apps with Few Pages and High Functionality per Page #893
-
|
For web apps like Notion Web or Figma Web Version, which don't have many pages but pack numerous features into a single page, how should we structure entities and widgets? Should we move components used only on a single page but clearly distinguishable as entities to the entity layer? Or since they aren't reused, is it better to keep them within the page itself? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
I'm watching from the business. If the business says that there is a certain function that fulfills the business scenario, then I put it in the feature. One page or more than one page is not important in this case. By dividing the page into layers according to the FSD methodology, you clearly mark out the areas of responsibility and then you can clearly explain to the business what is a feature or widget on this page. Entities are very easy to identify by having a unique id. |
Beta Was this translation helpful? Give feedback.
I'm watching from the business. If the business says that there is a certain function that fulfills the business scenario, then I put it in the feature. One page or more than one page is not important in this case. By dividing the page into layers according to the FSD methodology, you clearly mark out the areas of responsibility and then you can clearly explain to the business what is a feature or widget on this page. Entities are very easy to identify by having a unique id.