Based on my own experience... it depends. I explain it... First of all you should create a very robust asociative model that will serve as a base for all the design objects you want or need to create. This model will allow to to fast create all the future objects but not forgetting about the performance. In a common project this part shoult take the 30% of the time (with a medium complexity sources of information). Designing would take a 50% of the time, and the spare 20% for testing, documents, etc.
In my case, I spend much time with script as I want to assure that the asociative model is easy, robust and scalable. If you get this, as I said, you can develop faster the interface using less complex expresions and navigation modes...
Anyway with this topic too many books could be written!
Many thank you for your sharing. I am strongly agree with you that to have a very good data model which take care of the field name and link all the table which is required and bring in all the field that require in future .
So that is one of the reasons that user who already learn to Qlik View script , very un-likely to other DV software , which i think for this Qlik View have a advantages.
As there are so many helpful people in this forum who are so willing to share their knowledge.
In fact now i am learning how to develop good data model ,from your blog post at below :-
And thank you for help me with the script to kick start on below link , which i already tested working fine , now i can reduce a lot of Tab by make use of loop to load multiple raw data just using one script :-