Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "design mockups"
-
So my school got invited to this coding competition for high-schoolers and among them, I was a part member and part mentor along side our CS professor since I was the most proficient coding stuff (although most of I do were JS and Python stuff although i can read other code)
Then this guy showed up.
He was picked by the faculty to take the WebDev competition. He knows how to use Photoshop for Photo retouchings and stuff but here's a problem.
He can't code nor make a proper website design.
So being the kind person I am, I volunteered to teach him what I know about frontend and HTML. This goes on for 4 weeks of nonstop practices, coding sessions and finally, Code In The Dark-style practice (which involves the person to code a full website for only 15 minutes).
When he was able to finish and mastered some of what I taught. I gave him the go signal and we were on to the road to victory.
Unfortunately our first try, we won nothing.
He said after the competition "I give up man, I can't take this!" but I said, "Just because you lost a f*cking competition once, doesn't mean you're a motherf*cking loser in life. There's still one more chance."
So I pressured our WebDev guy to be more better, taught him about mockups, JavaScript and etc.
Then the second attempt a year later, me and the WebDev guy won and moved on the finals. However, he didn't win the finals and I was the lone champion reprsenting our school.
Although he didn't win, he was happy I carried the torch and win the prize.
Prior to that, he asked me "Hey, how to be like you?"
I only answered, "Achievements are just gold with cloth and paper. Wear it lightly".
Fast forward to today, he's now the school's head design coordinator and layout designer for their newspaper column. He also practices his coding skills by frequenting on our coding sessions even when the competition was over.
But whenever someone asks "who taught you this?" he would only look to me, smile and say "that person right there".7 -
** Makes a design for a landing page, in a Single-page format. My designs are usually clean and "aerated" (breathing, uncluttered). **
** Pm comes in **
Me: Oh hey! I've finished my mockups
PM: Ah nice, let's see... ** comes to my screen **
---
PM: Not bad, but can you remove this spacing, this spacing, and this one and this one... oh and that one too?
** corrects them as she says, everything starts looking cluttered and I dislike it **
PM: Great! Can you export them in pdf?
Me: Sure.
** PM goes away **
** Proceeds to re-make the mockups more "breathing" with an evil smirk **9 -
Let me preface this by saying I'm not a designer.
While I can make individual bits of a site look good, and I'm actually pretty skilled with CSS/Sass, overall design completely escapes me. I can't come up with good designs, nor do I really understand *why* good designs are good. It's just not something I can do, which feels really weird to say. but it's true.
So, when I made the Surfboard site (that's the project's internal name), I hacked everything together and focused on the functionality, and later did a branding and responsive pass. I managed to make the site look quite nice, and made it scale well across sizes/devices despite being completely new to responsiveness. (I'm proud, okay? deal.)
After lots of me asking (in response to people loudly complaining that the UI doesn't have X feature, scale properly on Y device, and doesn't look as good as Z site), the company finally reached out to its UI contractor who does their design work. After a week or two, he sent a few mockups.
The mockups consisted of my existing design with a darker background, much better buttons, several different header bars (a different color) with different logo/text placements, and several restyled steppers. He also removed a couple of drop shadows and made some very minor styling changes (bold text, some copy edits). Oh, he also changed the branding colors. Nothing else changed. It's basically the same exact site but a few things look a little better. and the branding is different.
My intermediary with the designer asked for "any feedback before finalizing the designs" -- which I thought odd because he sent mocks for two out of the ten pages (nine plus a 404 page). (Nevermind most of the mocks showed controls from the wrong page...).
So, I typed up a full page of feedback. Much of it was asking for specifics such as responsive sizing on the new header layout, how the new button layout would work for different button counts, asking for the multitude of missing pages/components, asking why the new colors don't match the rest of our branding, etc. I also added a personal nitpick about flat-looking controls because I fucking hate them. Everything I wrote was very friendly and professional.
... His response was full of gems. Let me share a few.
1. "Everything about the current onboarding site looks like a complete after-thought." (After submitting a design basically identical to mine! gg!)
2. "Yes [the colors match our current branding]." (No. They don't. I checked. The dark grey is different, the medium grey is different, the silver is different, the light blue is different. He even changed the goddamn color of the goddamn LOGO for fuck's sake! How the fuck is that "matching"?!)
3. "Appreciate the feedback [re: overlapping colored boxes, aka 'flat'], design is certainly subjective. However, this is the direction we are going." (yet it differs from the rest of our already-redesigned sites you're basing this off. and it's ugly as shit. gg again :/)
4. "Just looked at the 404 page. It looks pretty bad, and reflects very poorly on the [brand name] brand. Definitely will make a change here!" (Hey! I love that thing. It's a tilted, dotted outline of a missing [brand product] entirely drawn with CSS. It has a light gray "???" underlay and some 404 text inside. Everyone I showed it to, coworkers and otherwise, loved it. "Looks pretty bad". fuck you.)
I know I shouldn't judge someone so quickly, but what the fuck. This guy reminds me of one of those pompous artists/actors who's better than everyone and who can never be wrong, even while they're contradicting themselves.
just.
asfjasfk;ajsg;klsadfhas;kldfjsdl.undefined surfboard another rant about the same project long rant pompous designer apples and asteroids design8 -
Just before you, my fellow system programmer, scroll past this, let me say this:
🍬 The web is actiually simple. 🍬
Both HTML and CSS is declarative. It's all easy when you understand the concepts, learn how to be idiomatic and quit trying to do that imperative bullshit in languages that aren't imperative.
HTML is simple. You know the boilerplate: doctype, head, body, that's all. Just mark it up and do NOT look at it before you end, mark it up as it were article or something. The appearance is up to css.
CSS is simple. You may even forget bem or rscss, you're already a skilled software developer. Use common sense and your code-splitting and naming skills you gained reading The Code Complete or doing software development for years.
Forget mockups. Forget absolute positioning, forget setting width and height in pixels. Go to awwwards, find some inspiration. Draw some buttons and fields on paper with your good old pencil. Then go and write some css. Feel free to steal some shadows and transitions from codepen.
Read about 8-pixel grid system. Let every element push away from others by setting something like margin: 16px; and whoops! You've just got fully responsive and got great vertical rhythm without even using media queries!
Oh my god, do NEVER set width and height explicitly! Type something like button { width: 120px; } and bang! The entire web page is broken. Quit that shit. Let it resize as it should. It will resize itself to fit its contents.
HTML is by default ready for your template engine. That's how you receive data from server — as server-side rendered, plain old HTML page. On the other hand, the form element is the most axiomatic and simple way to send the data to server. That's how you send it — as plain old GET or POST that every webserver can handle.
All of there are true:
1. It's easy to get great 100% responsiveness without media queries.
2. It's easy to align items in row, it's just one line of css. Maybe two, if you still want elements to wrap, but want to use flexbox:
.parent {
display: flex;
flex-wrap: wrap;
}
3. HTML and CSS are fast by default.
4. You don't need mockups to achieve great visual experience. Mockups is imperative, web is declarative.
5. You may not even need JavaScript to make great website.
Go on, ask me a question about web! I'll ready to answer everything.21 -
So far all designers I worked with do the following:
1. Use "creativity" to come up with stuff that the system does not allow implementing, for example: Changing clock color in mobile statusbar to Blue!
2. Use "creativity" to come up with a heavily customized calendar for a windows software which requires building the control from scratch, but they explain their creativity by saying: Can't you use CSS?
3. Provide iOS only design which follows android guidelines and refuse to provide android styles for at least pages that to be handled differently on each platform, for example, we had a checkout page in an app, and they wanted the same style for both WITHOUT building custom control for it, they said: Can't you use the android custom control inside iOS
4. They design for a website and send same mockups for me to implement on mobile apps, the problem is a web page runs on a big screen when the mobile app doesn't have room for half the stuff they designed but they must look exactly the same as website !!
5. They send entire PSD with no color codes and say: You can extract icons, and colors from psd ... When they should provide them as per our request which is: SVG for Android and PDF for iOS with the color codes, but no, they are lazy!
6. They ask the team to create a page in the app which is almost production ready just so that they test different font sizes and see how it will look on the phone
7. Same as #6 for images that contain text
The list goes on, but those are by the far the ones that made me one step away from resigning, some of them made me resign...6 -
We needed a design for our Android and iOS App, everything should be done by an award-winning design agency. What we received was only a design for iPhone X. Only mockups as PDF, no icons, nothing. So we requested the Android design and an iPhone 8 one including icons, color codes and whatnot.
1 FUCKING MONTH LATER we got the new designs... They are all the FUCKING SAME DESIGN where some mockups were "displayed" on an android phone, and some on an iPhone. Still no icons though.
3 weeks pass and we geht FUCKING sketch files, to extract the shit ourselves. Thank you for nothing.
It took again nearly 3 month to get a "proper" Android design and all the assets. You could clearly see, that they never did anything for Android but well, we had to work with it. Award-winning design agancy my ass.5 -
Start-ups and corporations trying new things be like:
"Why should we pay a developer or a company to develop this and this for us when we can just:
- start a competition.
- get free design mockups and code.
- decide which is better.
- reward a small prize and maybe some freebies to the competitors.
- profit. FREE CHEAP CODE AND DESIGNS!!!"
It might be the reasonable and logical thing to do from a business standpoint if its about code you need to rarely maintain..
But from an independent developer viewpoint - FUCK YOU AND THE SLOW ENSLAVEMENT OF MY SPECIE!!!3 -
You want me to build a whole fucking site with a new theme on December with no mockups and all build with a custom design after you left me all fucking September and october without fucking work?.
No. Fucking. Way.1 -
A few years ago I was working in a startup where the designer was given way too much decisional power (he was friends with the owner).
He had a tendency to keep editing parts of the design during the development phases, so when we had to work on a new big section of the application, before starting the tront-end development, I asked him to confirm that the mockups were final.
He confirmed the design was final and was not going to change.
10 days later, of couse, he sent a new, completely different, set of mockups. The startup owner expected the new design to be implemented without moving the deadline.
(I left that startup shortly after. The issues with the designer were just the tip of the iceberg.
The owner tried to keep a payment hostage to "force" me to sign a new 1 year contract. He backtracked when he thought I was recording the call. I got my payment and left.)1 -
My first project it’s an emotional roller coaster. I was a little trainee/ junior dev at my job with a little more than a month learning RoR and one day my tech lead receives an email from the big boss saying: “We got a big client who wants a total redesign of his web and we said yes we can do it in a month, so please check if anything it’s reusable”, after reading my tech lead said to me “Do you want to help me with this ?” And well, we spend like 2-3 hours checking all the controllers, views, assets, etc. We conclude that the project was mostly front end changes and the back end will stay the same, so yeah it can be done in a month. The next day in a meeting with all the team I was nominee to be the person in charge of that project, because it was an easy project and all my teammates hate to do front end stuff, so I take the challenge. After that I met the Project Manager, another guy who recently start as PM about a month, so yeah we were two new guys who need to handle the project of a big client, nothing can go wrong. We did the planing, I give an estimation ( first one in my life ) for the tasks and added like 4 hours in case anything goes wrong. Then the first sprint came by, and I couldn’t finish it because the time given to some features was to low and the “design” was a mockup made by the PM, ok, no problems, we add more time to the tasks and we ask for a real design. At the half of the sprint the client start adding more and more stuff, the PM doesn’t talk back, just say yes yes yes. Then in a blink of an eye the easy project became a three months projects with no design at all, two devs ( a new guy who recently begin as dev enter the project ), just mockups and good hopes. But somehow we did it, we finish it! Nope. The early Monday of the next week I received an email of the PM saying we would have a second version and the estimation of the tech lead was a minimum of six months ( that became 8 months). This time was hell, because the client doesn’t decide what the hell he wants so a task would take a couple of days more or so, the PM became the personal bitch of the client, but it wasn’t his fault, because we later knew that the company became partner with this client and because of that the PM didn’t have too much choice :/, the designs were cool, but they weren’t on time ever, our only design guy had to do designs to our project and another 5 projects of the company, so yeah, we weren’t the only ones suffering. At the end we survive, the project was done and the client somehow was happy. Of course the project didn’t end and it was terminated half a year later, but I’ll always remember it because thanks to this project I was given the opportunity to work as a Front end dev and I’m happy still working as one.
-
I work with a designer who provides me with the mockups of the websites we do where I work. We use Figma, which is a tool similar to Sketch. I do design myself and with this tool is quite easy to mockup sites.
This designer is the worst person I've ever met in terms of document organization. He never organizes the layers of the documents, or even cares to assign names to each layer. It's not that hard with simple designs but when it comes to develop a full website it becomes awful.
I've been asking him politely to organice those documents into layers and groups for almost three years to which he never does.
I'm not able to find the proper words to ask again politely and when I do, he just puts the layers without order into a bunch of groups and calls the job done.
How hard is to be a bit emphatic to your coworkers and spend 5 minutes of your time making their life easier?4 -
Schrodingers font size:
When you follow the directions given in the style guide, but it still doesn't match the mockups.
The chosen font size can be considered both wrong and right until examined by a member of the design team. -
I did a communication and multimedia design study because I was convinced I already knew almost anything.
Ooh the beauty of youth.
But it did help me in the long run, communication with clients and being able to present work with some decent looking presentation and mockups gets the managers all horney as teenagers on springbreak.
Pretty sure thats why I beat some competitors on big projects while their technical skill and team where much better.1 -
My worst experience with a designer was when one forgot to design the website mock up for 2 weeks... so I just did it myself. Thankfully I have a degree in both development & design and bullshited my way through it. We were swamped at the time so I wasnt too thrilled to be doing his job. He somehow still has a job here, even though he's lazy and his mockups suck. 🤐😵👎
-
I am going to rant about this here because there is nowhere else where I can "SCREAM".
My work process....
Working on a project that does not have mockups nor a plan. I am building as I go. Design, infrastructure, EVERYTHING. Because my boss is a "genius".
And the project goes like this....
1. Boss tells me to build something.
2. I tell him the functionalities and design.
3. Boss, "Figure out yourself and we will see how it goes".
4. Me, Builds something.
5. Boss does not like it and demands changes.
6. I make the changes.
7. Repeat.
1 year and a half for one project that is a simple e-commerce. Show the products, a search functionality, users sign in and can order and show their orders.
A simple page in which does not take time, but without a plan, without A FUCKING PLAN this project will go on forever.
I am losing my mind. I put on test and tell my boss to test it for bugs. He demands a meeting and tells me, "we need to add this".
OH FOR FUCKS SAKE. TEST THE SITE FOR BUGS YOU FUCKING USELESS THING. I WILL FIX THE BUGS AND THEN WE WILL TALK FOR NEW MODULES.
I am doing documentation, database infrastructure, front-end, back-end, testing (because my boss cannot do it. It took him 2 week to start testing for some things after asking him every fucking day "Did you test it", "Did you test it").
Maintaining out CRM for bugs and new modules and maintaining our company's website.4 -
Context: large project moves to touch friendly UI, request and initial specs late last year, specs initial mockups early this year, designer promises final design before end of Q1.
Two sprints into development no fucking design, meeting today about it, designer has no fucking clue about what we actually agreed to last time. Promises again to have it for next time.
What the actual fuck? How difficult it is to least read up the fucking notes and do your fucking job that you are being paid for? Had a half fucking year!
After meeting...
Me: why do we even keep him around?
Pm: he is really overbooked...
Me: my balls are overbooked, don't promise if you can't deliver! (Leaves meeting room)
Fairly confident that this is the last project with this guy...
Am I the only one who just hates working with designers?2 -
TL;DR: Have you ever been on a serious company where you have to DRAW a high fidelity mockup of the software in the design phase?
So I'm in my last year of college and I have a class called Interactive systems design, which is basically about usability and how to design the frontend of your app so it's intuitive, pretty and easy to use.
So we work in groups to design a project for the entire semester, following a long and tedious process of research and planning which includes writing absurdly long documents, doing interviews with potential users and more.
Now that we've done all of that, the teacher insists that we make paper mockups of our app before we do a digital one using Balsamiq or other programs. He wants the paper mockups to be "interactive", so we have to draw them and then record a video where someone "clicks" on the mockup with their fingers and another person moves the papers around to make it look like an actual app that's doing something.
The teacher still insists this is something almost every company does when designing a project, so it's very important that we learn to do this kind of stuff. He's kidding, right? Have you guys ever drawn a mockup of an app instead of using some mockup software?7 -
First post and of course it's a rant.
I work for a mid sized development agency with approx 50 developers heading up the main development backend team.
So, on this one project the head of design goes through the client agreed spec but starts adding loads off additional UI elements and data that isn't in the spec, isn't collected anywhere and isn't needed
When reviewing the mock ups I raise this and push back saying it all needs to be taken out as we dont have that data and that the additional elements are not recoverable in the sprint time.
Designer sends the mockups to the client anyway and gets sign off from the client, who now expects all this additional work in the same sprint and at no extra cost to what we agreed for the sprint.
After an aggravating day trying to figure wtf we are going to do, I end up working until 3am (having started at 8am the previous day) implementing the addition shit, which needed to be collected and surfaced throughout the entire back end.
Owner of the business walks in this morning and gets told by the management team about how late I was working and what had gone on.
His response........
Pay for all employees in the business to have a takeout lunch on the company.
Best of it all, I was so busy catching up on the shit I should have been doing, that I didnt even get my free food!!!!
Why do designers think everything is so simple and just takes a few key presses?!?1 -
UX/design departments have process, review and do lots of work designing standard look and components for our front end. We use these.
Sometimes when they give us a mockups for new features they break their own rules/components.
Why are you handing me non-standard designs/components, when you made the standard ones and we could just reuse those.2 -
!rant
So "design" keeps sending me unfinished and unpolished mockups, I end up erasing what I got already done, and start over; Fun times yay.2 -
So we are nearly in 2018 yeah...
Today I received a "web design" and mockups were exported (by a design agency), in pdf...
That is too much for me. I take my day off.6 -
The photoshop failed me in designing the website so is there some nice fast design tool you are using to make some mockups?6
-
Right, budget constraints, in out project. Shop site. Lets go with a good online shop system (shopwired) and just brand up a suitable theme. Client wants to see design flats prior to starting. OK brief designer. Pick one of the themes that is close to their current brand styling. Grab the theme pages, set your browser to 1280. Mock up over the top with brand colours/fonts etc in Indesign and png the pages over to me (make sure we have them on google fonts). Designer comes back a few days later with branded up theme page visuals. Cool, they look great, shouldn’t take too long to rework the css and get this thing working. Client approves mockups. Great, so open the theme files and realise the designer has fucking moved stuff around. This has turned into something more than a styling job. Fucking hell. there goes my budget and deadline. Why don’t you designers ever fucking listen!!!!!
I should’ve done it myself but needed to save time as I’m already busy. Fuck, fuck, fuck, fuck, fuck, fuck, fuck! -
Building mockups while getting used to the design tool for two days straight. I don't remember doing mockups was this tiresome - wish I went straight to the code.