Skip to main content

Developer Viewpoint: Rapid Prototyping with SketchFlow

You can see my own direct review of SketchFlow here.

This article is a great introduction to SketchFlow, which is found in Microsoft's Expression Blend.

Rapid Prototyping with SketchFlow

Unlike developer "design" tools, SketchFlow is really great at focusing on the interface and how users will interact with the application. I'm not a graphics designer so I know pretty much right off the bat, my prototype may not have the prettiest graphics designs. However, with Expression Blend, I was able to make the UI look half-decent.

It uses XAML files to show case the interface - this is extremely useful as I just grabbed some earlier work being done in Visual Studio and dropped it in - worked like a charm. I was then able to make changes to the XAML from a designer's perspective instead of a developer's.

With the SketchFlow Map, you simply draw lines to create a flow between "pages" of your application or to integrate shared components. When you build your application, it provides a SketchFlow viewer with a navigation bar on the right. You can also add animations and direct content to create more interactive shots.

Now to present it, you can do a manual presentation (F5) and walk users through it - but one of the killer features is the ability to "package" the flow and give clients an application that they can walk through on their own, see your annotations or add their own and then send you feedback directly.

I'm a big fan of usability testing and while Sketchflow certainly is more on the prototyping side, it really does let you test concepts very easily.

If you're happy with what you've done, you can actually re-use the XAML and components you've built.

The Expression Blend evaluation period is 60 days - so it definitely gives you lots of time to work with it, even just for prototyping out concepts.

Comments

Popular posts from this blog

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site:

http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html



What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older.

Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments.

But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward.

Well, that explains CodePlex...

In a move that will be sure to anger open source (or rather anti-paid software, anti-Microsoft open source)  zealots, Microsoft is planning to buy GitHub.

A year ago, I mused about why Microsoft would shut down CodePlex and how the world needs competing source code repositories to be strong. I'm not the only one per this Slashdot article :
"...people have warned about GitHub becoming as large as it did as problematic because it concentrates too much of the power to make or break the open source world in a single entity, moreso because there were valid questions about GitHubs financial viability...." - Jacques Mattheij

I will be interested in seeing this play out - whether developers jump ship or not. Have all the efforts Microsoft has made in pushing towards open source be seen as genuine or will all the zealots jump ship or maybe even attack?

Microsoft's comment about why they shut down CodePlex referred to how spammers were using CodePlex. Well, GitHub has its own …

The World of Updates Today

I just received an update for Office 365. It certainly includes some cool features - including starting in one environment and picking it up in another environment. In recent years, I've certainly enjoined the use of Continuity on a Mac and in fact, I feel spoiled being able to start a message in one environment (even Google) and then finish it off on another.  This has become some pervasive when we were reviewing our most recent backlog at a client site, a similar feature was added to the current workload.

But with web applications, the trend is to reduce the amount of software on a client machine. I used to have automatic backup for all of my machines (thanks Carbonite!) but these days, many of my machines don't need anything beyond the core OS and some basic applications. Certainly that's the feeling with Chromebooks and even the lightweight aspect of many iOS apps. The functionality is mostly in the cloud.

When you upgrade your system, you expect it to a big update. So…