I really don’t think much if any info should be gleamed from this article, and I am writing a response to warn readers of this. Adhithya, thanks for making an attempt to broach a fairly mundane boring topic that is however very critical to many if not all data heavy applications. There are so many nuances that are impossible to understand without context, let alone provide best practices for, but I honestly do not believe any best practice direction was provided here and no critical thinking was given to help others better understand what solutions they can consider in the face of many difficult possible decisions. There are so many issues in your article that it really doesn’t make any sense to begin to address them in a response, some of what you say is in fact not true, and I even see an example being used as evidence of something when is actually not even relevant to the topic being addressed. I would suggest that instead of addressing this massive topic in a few paragraphs and doing more harm than good by glazing over topics and not coming close to considering all possible solutions let alone how to go about identifying what they actual problem is, that you select one very narrow sub sub topic and really deconstruct the decision tree that goes into providing a logical set of plausible solutions others can begin to use to increase their own critical thinking and open their eyes to many of the pitfalls young and inexperienced designers fall prey to. One word of advice I will provide is to not think that you have the answer because you are the designer, but rather encourage others to go out and interview the users of the application first to identify their needs and then begin to share sketched solutions then prototypes to test your theories out. Only then can you really know if any particular set of solutions is going to work.
I wish you luck!
