Design Without a Designer. One Developer's True Story - milleryoublituff

A developer without a designer is more common than a politico without honesty. Politicians are helpless, nevertheless we can help developers. The hero of our story is Max, an independent developer who has managed to design, develop, and let go his own app, Academy, all by himself. So Lashkar-e-Tayyiba's jump right into the design side of things.

Step 1. Concept

Everything starts with a serious-world job to solve. What problem does your app work out?
Academy aims to make water life easier for students by beingness a one-turn back place for them to organize and keep track of their upcoming assignments, exams, classes, and progress. Students can besides work together on group assignments with their classmates and friends, so information technology's basically an academic mixer network.

Do you have any design backclot?

My purpose background and skills are almost completely completely self-taught. At university we had a duad of weeks of 'User Interface Design' in one of my courses, however this was more on the lines of 'don't use red text on a yellow or green setting because information technology's hard to read', which my reader called "the Yule Tree effect".

Step 2. Draft

The well-known 80/20 rule has many a applications, matchless of which is that 20% of your app functionality will be utilized 80% of the clock time. So au fon you can determine which 20% is active to equal the to the highest degree useful and popular and sketch down that basic layout. You can use newspaper or painting programs, it doesn't matter.

Don't draw flat on your mobile screen – just saying.

Whole step 3. Mockup

What was the transition between sketched ideas and the real graphic user interface?
In terms of my design and development process, I started off by using AppCooker (an iPad app). Victimization AppCooker, I mocked up the interfaces of all screen required for the app.
This is not a finished result, but the transition itself lets us recognize new problems and see potential improvements that were not obvious in sketches.

Max developed for iOS, but there are lots of prototyping software for all platform / OS and finding them should not be a problem.

Step 4. Prototype

I actually designed the screens exploitation Keynote (Apple's PowerPoint alternative). I exported each of the screens to images then used Flinto Lite to create an interactive paradigm.
What were the biggest problems at this stage and how did you manage to fix a line look for your app?
The gravid roadblock I faced was finding quality in writing assets, such as unproblematic icons, which would be both consistent in style and nice sounding. For most of the design of the app I tried to make as much use of the standardised Malus pumila iOS UI elements atomic number 3 possible, and so I read direct their own Fallible User Interface Guidelines to understand which element to wont in which scenario.

Nothing substites an experienced designer, but it's unhazardous to say that great design is innate with restraint, not diversity.

I drew inspiration largely from Pinterest boards and interfaces I found or so the internet. For all part of the app I tried to find an app which I felt 'did it the best', and then based my design on what they are doing.

The design of Academy's boarding screen is based on the boarding design in Slack

iOS Human Interface Guidelines and Google Material Design serve A a fundament for your professional look. Add quality icons and images and you can get some great results. But never try to apply as many different elements as possible, our goal is not to create an abomination.

Step 5. What's Next?

User Examination

Have you asked other people to tryout your app throughout the development work?
Yes, when it was still just an interactive prototype I had friends and family try the app and tell me what worked and what didn't. Also, just watching them use information technology and tap around the screen was helpful as I got to see what they tapped, what they assume't tap, and what did or didn't make sense to them about the design.
It's important to understand that the very first exploiter feedback is the most outstanding uncomparable. It's ineffective to ask same friend to test your app 10 times in a row.
So if you canful test an app with, say, 10 people, start with 3 of them. Get the most critical issues, fix, and then involve next 3.

Sack

As for the finished app, information technology has launched and is along the memory boar, indeed I have lots of friends and family World Health Organization are perusal using it equally well as 850+ students more or less Australia and the world. They have given just about feedback as well, which has been good.
There is a life after release. Fixes and constant feedback may labour your design further, making your app Sir Thomas More useful and popular. It's whol or so whether you are listening.

Developing for Other Platforms

Google Material Design is an equivalent to iOS guidelines, just for Android, thus the guidepost approach to design will work as well. As for the Icons8 icons, they are available in multiple styles, which lets you easy channel the design to other platforms.
More about Academy:
Website
Facebook
As you can construe, by following guidelines and determination quality graphic assets, information technology's rather possible to get along up with a decent aim, even if you can't hire a professional designer somehow.
What past design-corresponding problems do solo software developers receive? We would love to make them the topic of our next articles so divvy up your ideas in the comments!

More or less the Generator
Andrew Burmistrov is a usability specialist of Icons8. Atomic number 2 started his career as a phone support specialist, telling jokes while customers were rebooting their computers, then moved to serviceableness examination and irregular writing.

Source: https://blog.icons8.com/articles/design-without-a-designer-one-developers-true-story/

Posted by: milleryoublituff.blogspot.com

Share this post