Client insisting on Vanilla JS instead of using a existing framework to design a reporting dashboard, because "first I want to build one dashboard page and see how people react to It and what all changes they want. Once we have complete picture in mind we will go for a framework". Sure, let's do the entire work twice for peanuts.

@HelloItsMe true... I work a lot on this kind of projects. Many times what you want to achieve by developing in vanilla JavaScript is later on being able to develop framework specific components (this is called framework-agnostic development).

It allows you not to depend on any specific framework, thus giving you more flexibility (imagine updating your code base from Angular 1 through 6 or if a specific framework looses popularity or support).

This allows you to build a common core which you can use on any framework. Then you can move on developing framework specific components.

If you want your library/component to be reused, this is the right way to do it.

@HelloItsMe No he does not want to us to develop our own dashboard framework (that would be an entirely different issue, imagine code complexity...cross browser issues). He simply wants it done in Plain Javascript, and then use a framework later when he is happy with the product (which I dread will be a mess of rapidly changing features). He just thinks that using a framework is bad in early stages, even though it perfectly suits his requirements and budget.

When you say "vanilla" JS and "no framework", does that exclude libraries like jQuery, bootstrap and the like? I mean, there's really no reason to reinvent the wheel in terms of grid techniques etc here if what you're doing is simply prototyping.

At my place of work we use UX tools for these things, although you can pretty much get away with simple ms paint images or physical drawings most of the time. It seems very expensive to implement functionality for the purposes of UX.

@buried Yes, no libraries. Just Javascript. We gave him a choice between Angular/Vue, but he wants it done this way and then redo it in Angular later if he likes the product.

@shivam-singh is the client techy? Otherwise just use a framework xD they can tell me that I cant use something when having good reasons but not just because. At the end they will be happy because I saved them money and time.

@Codex404 the client is not techy, but has a tech advisor who advised him to do this ( we are freelancing ). He will check the code too. Apparently he is quite brilliant.

@shivam-singh
Well, if you're getting paid hourly, then that's great haha.

Just show them differences in estimates, then they can figure out if they're willing to put their money where their mouth is.

And when they complain you can simply say: Well, you wanted us to reinvent the wheel for a prototype, so we did.

Customers shouldn't get involved in technical details, like which framework or libraries you use. You just have to make sure to meet all functional and non-functional requirements, like support for IE6, and such. Choosing the right tools is your job and you should keep technology based questions far away from your customer most of the time.

If there are really restictions like using vanilla js, because he just wants to test the feature, either be happy and take the money, or tell your customer that using well know and widely used frameworks saves a lot of time and money and also saves time if you have to enhance that dashboard in the future.

@JAY505 Frameworks solve common problems and abstract existing complexities. It would be like saying using patterns is adding complexity. I mean, sure, but at least there's documentation for it. There are many reasons to not pick frameworks for a particular project. In this instance none of them apply.