---
title: "From a sketch on paper to Forager"
label: "Building Forager · 1"
series: "Building Forager"
question: "Can a sketch on paper become a user flow, a layout and a component?"
date: 2026-11-15
duration: PT9M55S # 10 min
video: https://www.youtube.com/watch?v=1VCkeiqDRbM
page: https://sadbacon.com/episodes/building-forager-1/
map_stop: "Forager"
---

# From a sketch on paper to Forager

Building Forager · 1 · Building Forager · 2026-11-15 · 10 min

**The question:** Can a sketch on paper become a user flow, a layout and a component?

I photograph four sketches and see whether Forager can turn them into a user flow, a layout and a component.

## Chapters

- [0:00](https://www.youtube.com/watch?v=1VCkeiqDRbM) Three boxes become three Places
- [0:58](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=58s) A page sketch becomes a Layout and its Parts
- [2:18](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=138s) The ambitious one: a whole card
- [5:11](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=311s) When Find Zones doesn't help, draw them
- [6:15](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=375s) Putting a component into a Layout
- [7:21](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=441s) It should feel like sketching
- [8:48](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=528s) Where the Object's Sheet comes in

## Article

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.

## Resources

- [IPEVO V4K document camera](https://www.ipevo.com/products/v4k) (tool): The document camera over my desk. Forager's Camera panel takes its pictures of my sketches.

## Transcript

From the video's captions. Times link to the video.

### Three boxes become three Places

[0:00](https://www.youtube.com/watch?v=1VCkeiqDRbM) Okay, so let's take a look at this experiment that I'm currently doing. Click on camera. We'll see we have this user flow starts to show up here on the camera. We'll see the three boxes in this particular flow and we're going to capture this.

[0:17](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=17s) Many of the things we're going to see in here are things that I'm just testing with just to get the general capability. A lot of the layout is just scaffolding for this particular test. Let's go ahead and find the zones here.

[0:33](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=33s) So that works pretty good. It picked up that there's this particular area here named board. This is card details and then global nav. Okay, this looks great. What I want to do is turn this into a user flow.

[0:49](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=49s) Looks pretty good. Got three different places represented here.

### A page sketch becomes a Layout and its Parts

[0:58](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=58s) So let's try another image. This time let's go with a layout.

[1:08](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=68s) Looks like this one took a little bit more time for the agent to complete finding the zones, but it looks like it did that.

[1:17](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=77s) We can see there's a header. Two action areas picked up the label on the side. This main content area, comments, secondary content footer. So it picked up everything pretty good. Okay, so what I want to do is actually turn this into a layout.

[1:31](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=91s) So let's do that. All right, let's see the layouts. Ah, here we go. Okay It looks pretty good. Let's make this a little bigger.

[1:45](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=105s) One of the things that I'm noticing here is I didn't rename this image, it just gave it a default sketch name. So I think if I try to rename the next image, it should pick it up. So I don't have to change that here. Let's type this. Let's see what that looks like.

[2:00](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=120s) So we can see it created all of these different parts of the layout. And I can go to the layout itself and. See it here.

[2:15](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=135s) Pretty good.

### The ambitious one: a whole card

[2:18](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=138s) OK, now let's see if we can do something. Else. This one's probably a bit too ambitious, but let's give it a shot. So now what we have here and what I'm trying to do is isolate this particular component here. I don't want the other elements will go inside here and let's see if we can find zones and what this does on something a bit more complicated.

[2:49](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=169s) OK, actually that's that's not bad at all. It it picked up most of the things and that's that's OK. Probably let's see. OK, I didn't specify keyboard delete, so I'm just going to have to manually do that in this prototype here. This particular thing is going to be part of the card, so we'll delete it.

[3:14](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=194s) OK, so we clean that up. Now what I want to do is turn this into a component. So let's see.

[3:23](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=203s) And we go, I clicked component is very abrupt. Switching over to this. So how I move from place to place to accomplish this particular task is going to take some work. But really what I'm trying to prove out here is is the is moving from sketch to something within the product experience that I can then add more meaning to. So I think this is working pretty good.

[3:48](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=228s) It did have a problem with all of those, all the icons that were here. So that that's something to look into. That also there was a lot going on in that row. It's probably pretty tricky, but it picked up the description pretty good. Looks like it identified this is a long text input.

[4:09](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=249s) It picked up the little chevron and. So that must be a menu, and then there was one icon here for tag. That picked up is an icon. Much of this here is going to have to be reworked. And this is this is kind of going into where else in the product does it need to integrate and interact with?

[4:32](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=272s) Ultimately, the goal here is to test this out and then have good connection to the object model such that the object model can start to populate some of these things. And we're attempting to do that here by saying, hey, what does this card actually connect to? I didn't have description on here in this test environments object model, but I just added it. And we can see it does pop up here. So it'll be something like this.

[4:58](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=298s) Yeah, this this works out pretty good. This is this is the direction I wanted to take this particular thing. So OK, we have a component, we have a layout, and we have flow.

### When Find Zones doesn't help, draw them

[5:11](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=311s) Let's try one more. OK, and this particular one, I want to get this component. And over here we have notes about this particular component. And for this one, the test here is I want to capture this particular component, but I don't want to capture any of this information. So let's go ahead and take a picture.

[5:31](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=331s) And let's try the find zones. Okay, and this time it wasn't very helpful. And here's a case where we just want to draw it ourselves. So it finds that pretty good on drag. And I'll call this...

[5:46](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=346s) And then this is the stuff we don't want.

[5:53](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=353s) It finds that pretty good, and we want to ignore this.

[5:58](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=358s) All right, pretty cool. Let's try component. Ah, okay. Well, this was an ambitious experiment. And all right, let's ignore that one.

[6:09](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=369s) Okay, so that's pretty interesting. And I think this is the right direction to go in.

### Putting a component into a Layout

[6:15](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=375s) Now what I want to do is see if I can get one of those components into this layout. And actually, I want to add it to this part right here, this main content. Now, I only loosely specified this in this particular experiment. So it's not going to be the way that I want it to work. The way that I think this might be built out is that I have a way of zooming into this particular part here.

[6:43](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=403s) And then once I'm in there, I can add that component. So let's see. But right now, I think I have to go in here. This temporary tray. Open this up, and then...

[7:00](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=420s) It would be nice to have named that better. But it's going to go there. Okay, and so I think it's there. The whole flow here is a bit all over the place because that wasn't really the point of the experiment. But we'll check out what it did.

[7:19](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=439s) Okay, so it added it there.

### It should feel like sketching

[7:21](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=441s) This is the idea. The idea is that this thing, if we want to dig in and specify, we can dig in and specify. The idea here is if it helps us make a better experience, a better design, then we can start adding this kind of detail. But for Forager itself, it's meant to feel more like sketching and supporting the discovery of what to do. Right?

[7:49](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=469s) The design is going to unfold over time and some things are going to be less clear when you start. And as things become known and as things become understood, you want a place to put that. You want a place to hold that context in such a way that the human can see it and reason about it. And the agent has all that context that it carries into every interaction. And that's the intention.

[8:17](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=497s) And I'm trying to find out where that boundary is. That's what this experiment was about. It's kind of like at first initially, I wanted to stick with just layouts and layouts parts and start adding details to each of these. But when I started heading, kind of sharing this and showing people, I think it was still a bit abstract. And so getting some sort of Balsamiq-like wireframe component is really what this test is about.

[8:44](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=524s) And then seeing how that might fit into the overall object model.

### Where the Object's Sheet comes in

[8:48](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=528s) And if we hop into Forager right now outside of that test environment, what I want to see here is when I'm in a canvas view and I zoom in and let's just say I'm working on this particular object model. And I want to understand more about one of these objects. And I click in to see its sheet.

[9:19](https://www.youtube.com/watch?v=1VCkeiqDRbM&t=559s) How can I make a connection with the layout and the components that tie into the things that I'm understanding and building out and here at this conceptual level? That's the intention. And actually now that we're here, the next thing you can see this is again scaffolding. That's something that's coming up that hopefully I'll be recording and sharing as well to show how do we rework the information in the sheet that started simple, but as things grow over time, it needs some rethinking and what do we do about it?

*10 min in all. The page with the video: https://sadbacon.com/episodes/building-forager-1/*
