1

"The design can't be implemented because of "

over 4 years ago from , front end developer

I've been in the industry roughly for 4 years. I do front end development most of the time. And front end development is a relative term, so basically I just do html or php templates with some presentational javascript. Web designers like working with me because i've got an "eye for design" as they say.

I don't like using plugins. Although there are things I can't live without like jQuery.

But there's much more stuff that you can easily do yourself - off canvas navigations, animated burger buttons, some slideshow slider and so on. They bloat your site, they add functions or css that you don't need or worse - they break something. And sometimes even adjusting the plugin to your needs takes more time than writing a required component by yourself.

Recently I was working in a team with backend developer and designer. We were creating an e-commerce website. The checkout page designer has done and i've coded didn't look like what it should look when connected to the shop. It simply looked broken.

"The design can't be implemented because of an e-commerce plugin" - our back end dev said. "Can't you do a custom checkout solution so it looks like in design?" - i've asked.

He looked at me like i was crazy. After a long discussion we still were at the point where "plugin works like that and we can't change it".

It left me wondering. Why are we using tools we can't fully customise or edit? Tools that limit us? Time savings? Or is it because it's simply easier?

Have you ever been in situations like this? Where you have to adjust, change or even sacrifice some of the functionality because it doesn't fit the backend developers requirements/needs ?

2 comments

  • Dan Maglasang, over 4 years ago

    I'm speaking as a client-facing engineer on a product focused team. When building with speed, it is easy to point to a tool and say, "let's just use this and save time". My philosophy is that the design should come before the tool is chosen. Otherwise, there isn't sufficient context as to whether or not a tool/framework/plugin/addon/etc... is either insufficient, sufficient enough, or overkill. Also when I say "design", I mean when it is in its final stages for us: when it has been user-validated to a certain degree of confidence and has been given engineering feedback about feasibility.

    0 points
  • Vincenzo Petito, over 4 years ago

    No you're not alone! This is the story of my life! Every time i created a UI for an app or website, then developers just use premade templates, plugin with a terrible behavior or interface and so on; and if i want the design be consistent with the one presented to the client, the answer is every time the same: "There's no time to do like you've made it"

    0 points