I took photos of four sketches with the camera over my desk and asked Forager (the design tool I’m building) to read them. This was an experiment: can a drawing on paper become a user flow, a layout and a component, something inside the product that I can keep adding meaning to? A lot of what’s on screen is scaffolding I put up just for this test.
Three boxes become three Places
The first sketch was a user flow: three boxes with arrows between them. I opened Forager’s Camera panel, took the picture and pressed Find Zones. Zones are the areas Forager finds in a photo (one for each box I drew, named by the words inside it). It found all three and named them Board, Card details and Global nav, which is what I’d written.
Then I turned the Zones into a user flow, and three Places showed up on the canvas (in Forager, a Place is somewhere a person does something, like a screen). Pretty good.
A page sketch becomes a Layout and its Parts
The second sketch was a page: a header, an area of actions down each side, the main content, comments, secondary content and a footer. Finding the Zones took the agent a little longer this time, but it got there. It even picked up the labels I’d written off to the side for the two action areas.
I turned it into a Layout, and Forager made a Part for each area. One small thing: I never renamed the photo, so the Layout kept a default sketch name. If I name the next picture first, it should pick that up.
The ambitious one: a whole card
The third sketch was probably a bit too ambitious. It’s a card’s whole form: a name, a long description, a toolbar of formatting buttons, a project menu, a tag and two buttons at the bottom. I wanted the form by itself, as a component, without anything around it.
Find Zones picked up most of it, which wasn’t bad at all. It read the description as a long text input, the little chevron as a menu, and the tag as an icon. It had a problem with the row of icons, though, and there’s a lot going on in that row. (I also hadn’t told the prototype that the Delete key should delete a Zone, so I removed one by hand.)
Clicking “a component” switched me over very abruptly, and how I move from place to place in Forager is going to take some work. That isn’t what I was testing. What I’m trying to prove out is the move from a sketch to something within the product that I can then add more meaning to. Much of this component will have to be reworked. The goal is a good connection to the object model (the Objects a design is about, and how they relate), so the model can start to fill in some of these things. I asked what this card actually connects to. The description wasn’t in the test environment’s object model, so I added it, and it showed up on the component.
So: a component, a layout and a flow.
When Find Zones doesn’t help, draw them
The last sketch was another component, with notes about it written beside it on the page. The test was to capture the component and none of the notes. This time Find Zones wasn’t very helpful, and that’s a case where you just draw the Zones yourself. Forager fits them to the marks pretty well as you drag. I drew the ones I wanted and told it to ignore the notes.
Then I asked for a component. Ah, okay. Well, this was an ambitious experiment. I set that one aside, though I still think this is the right direction.
Putting a component into a Layout
Next I wanted one of those components inside the Layout, in its main content Part. I only loosely specified this in the experiment, so it doesn’t work the way I want yet. The way I think it should work: you zoom into the Part, and once you’re inside it, you add the component. For now I went through a temporary tray of components instead (it would be nice to have named that better). The flow here is all over the place, but that wasn’t the point of the experiment. It did add the component to the main content.
It should feel like sketching
This is the idea. If we want to dig in and specify something, we can, and when it helps make a better experience, a better design, we start adding that kind of detail. But Forager itself is meant to feel more like sketching, and to support the discovery of what to do.
A design unfolds over time. Some things are less clear when you start. As things become known and understood, you want a place to put them: a place that holds that context so a person can see it and reason about it, and the agent carries all of it into every interaction. I’m trying to find out where that boundary is. That’s what this experiment was about.
At first I wanted to stick with Layouts and their Parts and add details to each. When I started sharing that with people, it still seemed a bit abstract. Getting to a Balsamiq-like wireframe component is what this test is about (Balsamiq is a wireframing tool whose drawings look sketched by hand), and then seeing how that fits into the overall object model.
Where the Object’s Sheet comes in
Outside the test environment, in Forager itself, here’s what I want. I’m on the canvas, zoomed in on an object model, and I want to understand more about one of its Objects, so I click in to see its Sheet (the panel that lists everything about an Object). How can I connect the Layout and the components to the things I’m understanding and building out at this conceptual level? That’s the intention.
The Sheet is scaffolding too. It started simple, and as things grow it needs rethinking. That’s coming up, and hopefully I’ll record it as well.