@lopazrich402 I guess different people have different opinions because each one has their own agenda. I've been in the Qlik game for 15 odd years now although your I have an opinion on your question (will answer below), if really always depends on various factors. Some companies like to build everything into Sense (or View in past) and others want to make Sense as "dumb" as possible (If I may use your word).
My opinion is always, "horses for causes". I'm a great advocate for smaller Qlik Sense apps, based on a specific business problem. This ensures quick reload, quick response, etc. If you have a scenario where you need lots more detail in your Sense app, then I suggest a second (more detailed) app. First one is more a dashboard feel with let's say monthly figures. The second app maybe detailed to daily figures, etc. Then there is also direct query, but that is a discussion for another day.
If you do have Qlik Compose for example, and make use of Data Marts, you can build your logic in there. This helps to flatten (lighten) the Qlik Sense app, which helps with performance. But at the end of the day, from source to target, the processing needs to happen somewhere. Finally, I will rather go for the "dumb" Sense app, especially when you want users to build own sheets and make use of the library.
Hope this helps
