The importance of a good concept, sketches and mockups

The assumption is that I am not a designer, or at least I don't consider myself such.
Very often when we start a new project, we immediately start writing code, or we have the strong temptation to do so.
I don't think that it is a good approach.

You can realize that the first time you get to work with some mock-ups.It is another world.
It is a aweosome world.
If you can't work with a designer, you should look for a good designer. As last choise, you can still do something alone.
It is not easy, it can't be easy, there are people who do it as a job.
I'am not able to teach anything about this field, but it is essential to know how to look at the sketches, or at least how to use a bit some tools.

If you want to make sketches, just a pencil and paper .....certainly need to know how to draw ...
I find so amazing the material that has released for free by Taylor Ling.
You can find here printable-a4-gui-sketching
Ok, download it, print it , take a pencil and draw your idea.
I have this idea in my head ... new navigation drawer, list with some actions, a simple detail view. Why not, a long press action in list...
Of course, is not so easy.. it is just an example.


Definitely not beautiful, but they give an idea ...
Now you can code it, more quickly.

We can try to go a bit more in there, but unpretentious.
We can download Stencils source from Android Developer.
Even in this case, Taylor reelased an awesome kit for Photoshop, and a screen flow template.

Now they are available for N4...I hope that in future they can be available also for N7 and N10.

Let's try this ... play a bit with the levels, masks, contents...
Navigation drawer..

A list..

A simple gesture as long press..


They look real ... but they are only mockups.
Here the flow

The scope of this post is not to explain how to use these tools, because as I have said can't do it ..
The real purpose is to understand that it is very important to make some sketches of the app, before starting to develop.
Save yourself a lot of time.

And for the more difficult projects?
For these, there are designers ..

Comments

Post a Comment

Popular posts from this blog

AntiPattern: freezing a UI with Broadcast Receiver

Image
The worst thing that can happen to your app's responsiveness is an "Application Not Responding" (ANR) dialog. In android guidelines we can read: In any situation in which your app performs a potentially lengthy operation, you should not perform the work on the UI thread , but instead create a worker thread and do most of the work there. This keeps the UI thread (which drives the user interface event loop) running and prevents the system from concluding that your code has frozen. It's very important to understand what is Main Thread . When an Android app is launched, the system creates a thread for the application which is known as the main thread. If you run up any project under the debugger in Eclipse you will see the main thread. If your app ties up the UI thread for more than 5 seconds or a BroadcastReceiver does not complete within 10 seconds, Android will throw up the Application Not Responding (ANR) dialog which gives the user the opportunity t
Read more

NotificationListenerService and kitkat

Image
Android 4.3 (API 18) introduced NotificationListenerService . I published a post about it a few months ago. Android 4.4 (API 19) added new features, and now we can have a lot of extra info about a notification (before we need to use reflection to read some info). As in 4.3,to use the NotificationListenerService we have to extend the NotificationListenerService and implement onNotificationPosted() and onNotificationRemoved() methods public class SimpleKitkatNotificationListener extends NotificationListenerService { @Override public void onNotificationPosted(StatusBarNotification sbn) { //.............. } @Override public void onNotificationRemoved(StatusBarNotification sbn) { //.............. } } Then we must declare the service in the manifest file with the BIND_NOTIFICATION_LISTENER_SERVICE permission and include an intent filter with the SERVICE_INTERFACE action
Read more

How to centralize the support libraries dependencies in gradle

Working with multi-modules project, it is very useful to centralize the dependencies, especially the support libraries. A very good way is to separate gradle build files, defining something like: root --gradleScript ----dependencies.gradle --module1 ----build.gradle --build.gradle In gradleScript/dependecies.gradle : ext { //Version supportLibrary = '22.2.1' //Support Libraries dependencies supportDependencies = [ design : "com.android.support:design:${supportLibrary}", recyclerView : "com.android.support:recyclerview-v7:${supportLibrary}", cardView : "com.android.support:cardview-v7:${supportLibrary}", appCompat : "com.android.support:appcompat-v7:${supportLibrary}", supportAnnotation: "com.android.support:support-annotations:${supportLibrary}", ] } In the top level file build.gradle
Read more