18 posts tagged “design”

Network monitoring is a pain in the neck. The major reason this is that way is party because it is a manual job for the most part. Writing scripts to automate, log and track information. But on the other hand, if we were to have a simple tool that shows the most important alerts front and center with a nice user interface - it is possible that network monitoring could be easier. Like this:

Here we can create an alert system on the right (always visible and automatically updating) and on the left hand side we can create column views. As an alternative to this, I was thinking of a canvas like area that we can zoom in and out of for context.

Here you can represent the monitoring objects of interest by icons and should there be any issues you add error, critical or warning icons to show that there is an issue. We could create different types of icons to represent things like servers, server applications, websites, clients, network routers, printers, fax machines and more. Best of all, we can maintain this is a small space since we are only displaying the most important information first.

I came up with a new design for my alter ego - theadvents - where I have a place to post project links, videos, and a mini-blog feed all on the home page. It hides a lot of the content from view so whenever people poke around I could have it display content. I was also thinking of having a live comment canvas where people can write comments and see others live (temporarily of course).

This way, the site can grow in content rather than be forced into it. :)

I know I can come up with something and it shall be launched! In the meantime, check out this new design I made. At some point I should actually put some content into the design, but I enjoy this. This one is called Plenatude.

It's not nearly as complete as the others, but I like the colored rays. I think I'll build on this one and get back to you. Here's another view without the navigation links, you can see the rays better.

I also made a "People's Software Manifesto". This should count as content.

Well, I launched Curbside Design, made a milllion bucks and now I'm on my next adventure (what? it can happen). Here's another sweet creative consulting company I'm working on. This one is called Cre8tive Software. I thought to put in some neat fractal effects into the background.

I even made a business card, check it out.

So far so good, if I can just work up to creating something that brings in the doeh - then I'll be set :D

Indeed, the news travels fast. I made another website recently (though I haven't actually registered anything or committed to ensuring its success), nevertheless I did make one. Gotta get critiqued somehow, here's the mockup:

What do you think? Oh, and I also made alternative banners which are chosen randomly on load. Here's one,
and here's another,
and another,
and one more for good measure.

Just a few more, I promise :)

UPDATE: Here's the other ones I forgot to add :P

Hello everyone, I'm back. I missed vox, did you miss me? Here's some things that you might of missed:

Prototyping through Mockups
A way to create really awesome and even usable prototypes using Microsoft Expression Blend.

Post Galaxy, your first callbacks
A simple, effective implementation of a chat client using WCF callbacks. Here's what you can expect:

    How many times have you suddenly "discovered" a feature about a certain software that could of possibly saved you hours of time had you known that feature before? It's all too typical to find hidden features in software these days. The problem isn't that designers intend to keep you from using such a feature, it's that the design limits them from "trying to put everything in front of the user". There's the first mistake - don't.

    There are some products that will put everything in front of the user while other products will only put a few things while hiding the rest from perspective. Users will either find themselves searching and searching for something that they need to get to or slow down the confusion and filter through all the unnecessary, even still - distracting - garbage in front of them.

    To avoid this scenario, designers can equip themselves with learning about what tasks are important to their users in addition to creating workflows. Most users can only get one thing done at a time. It's usually best to follow this idea of presenting things one at a time - wherever appropriate. For instance, instead of providing the textbox to post a new blog post, there is a Create button at the top of the page. I can see that when I need to accomplish that task, it's right there in front of me to get to it - without distractions.

    As a user we can be prone to wanting everything in front of us at every possible moment, but what we tend to forget is that we don't always need to get everything - everywhere - done at the same time. So, in supplement we complete tasks according to the context or point of focus we are in. At the same time, with respect to the designer, we need to understand that users need to be able to get out of context quickly - without seeking it out, which can lead to frustration. Simple things like - "I'm done", "Save", "Ready", "Back", "Previous" help users understand that they can navigate to other points of focus not only fast but very simply.

    There is an age-old saying that everything that can be thought of has already been created in some form or another. The problem that differs from every single scenario is not necessarily the practice that implements the solution but the entire product that shows itself through its main and completed interface. While the importance of lean and efficient code is and always will be there, there is of much greater importance to a product that can market itself. But let's take a step back at what great products entail in their user interfaces.

    There are a load of toolkits available to create graphical user interfaces today for the web, desktop and mobile but what most of these toolkits tend to do is supplement a key component in creating a product - showcasing originality. In fact, the greatest part about creating a new product is that you have full control over how your users are going to interact with it - you can choose to make task completion inherently difficult or inexplicably easy. In all of interaction design this is quite possibly the most important - work hardest on it over any other.

    The only successful product out of that market will be one that can differ itself in great interaction experience. Of course, creating that will not be easy and should not be taken lightly. Efficient code takes much thought into building algorithms that you can depend on. The same goes for interfaces in that successful products take much more thought, time and emotional presence into designing interfaces that you can depend on.

    Interaction design not only requires a bundle of testing but it requires a lot of personal experience. As a developer, it would be incredibly difficult to design a product without any familiarity to the end result. Without personal experience to the end product, emotional attachment will be bias in favor of ease of development. As an interaction designer it is important to remember that product experience to users, no matter what the product, count on tasks being obvious.

    Taking a quick glance at the two remotes above, what tasks can you determine will be obvious to complete. Let's suppose that the person will be watching TV in the dark. Without being able to look at the remote, will it be easy to figure out what buttons to press? The remote on the right uses differing shapes, placement and space around the buttons to distinguish tasks from one another. The user will be able to learn how to use the remote during daylight or under the light. Familiarity with the product soon begets the obvious nature to complete tasks.

    Of course, on the left, lights allow the user to see which button is which and how to complete a task like changing the channel. However, due to the number of buttons and the few spacing there is between them - the user will have to look at their remote every time they want to use it.

    Obvious interaction is not so obvious when it of course depends on perspective. Anyone on a team will have a differing perspective of obvious interaction when they are looking at the same product. However, the key point in making things obvious is about taking away prerequisites. So for instance, in the remote example lighting was taken away. Without looking at the remote which is easier? How often will the user need to relearn the interface? How long will it take to learn the interface the first time? These are a few important questions when thinking about obvious interaction.