Conflict between apps

I'm just starting to look into Akaunting apps, but it seems to me the way that the "modules" are setup they are certain to conflict with each other?

For example to alter output on core pages you have to completely replace the view with your own blade file...so how does this work if multiple apps want to alter the same pages?

For example I wrote a simple module to add "Sort Codes" for bank accounts, but I had to completely replace the create/edit/index views for bank accounts, so surely this is going to conflict with something like the Custom Fields app.

This seems like a fairly serious flaw in the system if you plan to have lots of community developed modules?

Or for something basic like my bank sort codes, should I be submitting this as a pull request to the core github repo instead of trying make it as a module?

Nope, there is no such conflict if you think it as a whole. Moreover, it's a managed app store so we review every line of the code of apps/modules before publishing.

First of all, while you can, you should avoid altering the whole page. There are tons of "stacks" everywhere:

https://akaunting.com/docs/developer-manual/overriding-output

Secondly, to add just one field, you should not create a module but use the Custom Fields app. Especially for features not usable worldwide.

Lastly, modules that change the existing table structure (like adding fields) are not acceptable, they may just create new tables.