How do you structure your app?

#webapp #discuss

We have a fairly large app currently organized at a high level into view, logic, model, communication, and utils. All files are aliased and we have scripts to handle any moves. For the most part we follow grouping by purpose, but it's still a bear to find things sometimes.

This is the second time our team has taken a shot at reorganizing so I'd love to hear about everyone's experience with this.

Example:

|-view
  |-engine
    |-core
    |-animation

  |-feature
    |-featureName

Top comments (2)

Martin Becker • Apr 23 '18 • Edited

I might separate it like this:

| root files
| - bin
| - lib
  | - engine
    | - sound
    | - graphics
    | - gui
  | - entity
     | - manager
     | - components
| - app/data/content
  | - entities
    | - mobs
    | - npcs
    | - items
  | - guis
    | - menu
    | - inventory
  | - models
  | - gfx
  | - shaders

Harry Dennen • Apr 24 '18

I've realized the most important part of this exercise is to make sure the structure guides a team to make the same decisions on where to put things. Whether they're good or bad isn't really relevant as long as everyone reaches the same conclusions when looking at the structure.

DEV Community

How do you structure your app?

Example:

Top comments (2)

Read next

Looking for some feedback on my team's new open-source secrets vault project.

I am purposefully super nice to AI because I imagine they are trained on data where nice people get better help. Doing this, though, has an existential uneasiness to it.

Types vs Interfaces

Meme Monday