YouTube2Text

Как построить cкринфлоу. Как превратить CJM в вайрфреймы. Зачем вообще нужны вайрфреймы? — Transcript

by Артур Кузьмин • Formfactor · 7,430 words · 1,112 segments · language en · Watch on YouTube

Full transcript

  1. 0:00Dasha won a prize. And today I’m
  2. 0:02going to design wireframes for her. But
  3. 0:05I’ll try, you know, not to design
  4. 0:07everything, because I think, well, you
  5. 0:09need to practice a bit yourself, too.
  6. 0:12Also, I’ll be doing the desktop
  7. 0:14version, because you can all handle the
  8. 0:16mobile one yourselves. So, what should
  9. 0:19I pick? I’ll take some standard frame
  10. 0:22that I usually work with, a small one,
  11. 0:25and start reading. Right now, I’ll
  12. 0:29try to quickly sketch out a wireframe
  13. 0:31and show you how it’s done. Basically
  14. 0:34, look, here is my task. I’m trying
  15. 0:36to turn the CGM into a screenflow. I
  16. 0:39have these major stages, right? And
  17. 0:45these big stages—acquisition,
  18. 0:46registration, activation, referrals,
  19. 0:48the user account, and all that other
  20. 0:50stuff—they represent a fairly
  21. 0:52standard pattern. For instance, with
  22. 0:56registration, you pick more or less
  23. 0:58what methods you’ll have, whether
  24. 1:01you'll use social logins, or if you'll
  25. 1:03have passwords or magic links. And on
  26. 1:07Mobbin, you can just find a service
  27. 1:09with a suitable registration and copy
  28. 1:11it directly from there. I mean, the
  29. 1:15whole set of screens you have is
  30. 1:17something that can be copied in full
  31. 1:20patterns. There are things—and most
  32. 1:24things, 90%of them—that you can just
  33. 1:27look up somewhere else. But then there
  34. 1:30are personal things. For example, we
  35. 1:32have a personal budget management
  36. 1:33service. Let's take a look. I won't
  37. 1:35look at any existing personal budget
  38. 1:37services; I'll try to design it purely
  39. 1:40based on the description, so you can
  40. 1:42see how it’s done. My goal, and as I
  41. 1:47understand it, every block here is, de
  42. 1:52facto, a screen—or at most, two
  43. 1:56screens. So, we try to break down these
  44. 2:01stages so that they ultimately
  45. 2:04correspond to the screens or screen
  46. 2:07states in our screenflow map. There we
  47. 2:10go. Let's get started. So, what do we
  48. 2:11have here? Acquisition, recommendations
  49. 2:13from friends, saw it on Instagram,
  50. 2:15found the app through trial and error.
  51. 2:16There’s clearly no interface here.
  52. 2:20Then, a landing page. Well, we have
  53. 2:22some kind of entry point. Actually,
  54. 2:26it’s even described here what should
  55. 2:28be on it. I won’t draw it for you.
  56. 2:31I’ll just mark it now as an entry
  57. 2:35point. I mean, you can label it however
  58. 2:38you like. Your map can have its own
  59. 2:40legend. I usually mark the entry point
  60. 2:44with a circle like this and write, well
  61. 2:47, this is my entry point. So, the
  62. 2:51traffic channels go into this entry
  63. 2:54point somehow. And then from the
  64. 2:57landing page, we move on to our product
  65. 3:01. Okay, I've saved that. Here is the
  66. 3:03Windows entry point. I won't be
  67. 3:05designing it. Then let's read on.
  68. 3:08Registration, registration. We need to
  69. 3:11understand what that is. If it's a
  70. 3:13mobile app, registration will be before
  71. 3:17onboarding, at the very beginning.
  72. 3:21Because that's the standard practice:
  73. 3:23first, a person provides their personal
  74. 3:25data, and then we interact with them.
  75. 3:27If it's a web service, the conversion
  76. 3:30is lower there. So, we can first let
  77. 3:34the user try out some intermediate
  78. 3:36features, and then they'll hit a
  79. 3:39limitation where, to save their user
  80. 3:41data, they need to create an account.
  81. 3:46Or we won't bother and just do it the
  82. 3:48same way, where the person gets an
  83. 3:49account first and then gets onboarded.
  84. 3:52In any case, why do we need an account?
  85. 3:55Because as soon as a person creates
  86. 3:58some user data, say, creates their
  87. 4:01first invoices or enters their expenses
  88. 4:04, we need to save it and link it to a
  89. 4:07specific person. And to do that, we
  90. 4:10need their account in the system.
  91. 4:13That's why I think that's what we'll do
  92. 4:18. Actually, whether onboarding or
  93. 4:20registration should come first is a
  94. 4:22matter for A/B testing. At the stage
  95. 4:25when the product is just being tested
  96. 4:28or just entering the market. You take
  97. 4:31two versions, try putting onboarding
  98. 4:33first, try putting registration first.
  99. 4:36Registration is quite a harsh step. If
  100. 4:39you have a strong offer, good branding,
  101. 4:43or you've shown some really appealing
  102. 4:46screenshots, or you have a killer
  103. 4:49feature, you can hit the user with a
  104. 4:52tough hook like: "Hey, you want this?
  105. 4:56You can have it all, but please
  106. 4:58register first." And many services can
  107. 5:01afford to do that. Just go for it right
  108. 5:05away. Especially if there's social
  109. 5:08media login, it's very easy to do. It's
  110. 5:11not as big of an effort as email
  111. 5:14verification or other similar things.
  112. 5:18Yeah. But opening up registration can
  113. 5:20be a hypothesis for a test. You know,
  114. 5:22for instance, that right now ChatGPT
  115. 5:24has removed the registration
  116. 5:26requirement. Well, like, you can use
  117. 5:29the bot for a little while without
  118. 5:31registering. I think they did—well, I
  119. 5:34haven't checked yet, but there's
  120. 5:36probably some mechanic where you make a
  121. 5:37few requests without registration, and
  122. 5:39then they tell you: "Want more? Please
  123. 5:42sign up." So, it's a test question. If
  124. 5:45we take registration, I'll just copy
  125. 5:48this down a bit, what are we doing here
  126. 5:52? Hmm, what are we doing here? Well, I
  127. 5:55could design this thing for you, but we
  128. 5:58don't have to waste time. I'll try to
  129. 6:01put it together quickly, but you'll
  130. 6:03still need to check after me. So,
  131. 6:06essentially, registration is just like
  132. 6:09mine. You can find any equivalent that
  133. 6:12suits you by looking on Bombine. But
  134. 6:17I'll have some large text there so I
  135. 6:20can see it clearly from a distance.
  136. 6:25There. And I'll just label it for them.
  137. 6:29To start, I usually just mark up the
  138. 6:31screens and label what should be on
  139. 6:33them. So, we have at least two screens
  140. 6:37here. That's login and registration. I
  141. 6:42mean, they might look completely
  142. 6:44identical, but usually, they just have
  143. 6:46different text. Then, after the person
  144. 6:51—well, here we need to decide right
  145. 6:55away, it says by email, by phone number
  146. 6:58, and via Google. So, how will that
  147. 7:02work? Are you looking for email login
  148. 7:05—with a password or without one? I'll
  149. 7:09warn you right now that a password flow
  150. 7:12is huge; it's a ton of things: linking
  151. 7:15accounts, email and social media, email
  152. 7:18and phone, phone and social media. In
  153. 7:22short, having that many login methods
  154. 7:24at the start can be very complex.
  155. 7:28Honestly, to simplify the service, if I
  156. 7:30were building an MVP, I would choose
  157. 7:32either email or phone to start. Yeah.
  158. 7:36And phone, I think, is the easiest.
  159. 7:38With a one-time code. So, if I had a
  160. 7:42phone with a one-time code—well, I
  161. 7:45probably won't even draw it now, I'll
  162. 7:48just label what's here; for some reason
  163. 7:51, everything I write is centered. I'll
  164. 7:54have that separately. I'll just write
  165. 7:58here that this is our scenario:
  166. 8:03registration via phone. So, everything
  167. 8:08she listed, I have to do all of that,
  168. 8:10like sign-in via social networks,
  169. 8:12registration via social networks. I
  170. 8:15mean, you see, how many scenarios is
  171. 8:17that already? That’s four already. So
  172. 8:19, if we have sign-in via social
  173. 8:22networks, then the sign-in window here
  174. 8:25should be the standard one. So it turns
  175. 8:28out I did it wrong; I shouldn't be
  176. 8:29duplicating this. Instead, I could have
  177. 8:33these four scenarios branching out from
  178. 8:37this window right here. Okay, sign-in
  179. 8:40by phone, registration by phone. Well,
  180. 8:42usually this is just one screen, just
  181. 8:45two states with different headers. And,
  182. 8:47well, it kind of redirects from one to
  183. 8:49registration, and from registration to
  184. 8:51sign-in. So they're like, "Brothers."
  185. 8:54Okay, sign-in by phone, registration by
  186. 8:56phone, sign-in via social networks,
  187. 8:57registration via social networks. If we
  188. 9:00sign in by phone, we have a one-time
  189. 9:03code here and here. So I’m mapping
  190. 9:06out for myself that I have these
  191. 9:08screens, they exist here and here, but
  192. 9:10they might differ slightly. Here, if I
  193. 9:13sign in via social networks, I’ll
  194. 9:17probably have nothing, or either
  195. 9:20nothing or an authorization page. There
  196. 9:24. Well, I mean, in short, there will be
  197. 9:27a Google page here that I’ll use to
  198. 9:29sign in. And here too, it doesn't
  199. 9:32matter if it's sign-in or registration,
  200. 9:33it’s like I’ll have the same page
  201. 9:35for both. But I separated them here
  202. 9:38because I’ll have two different
  203. 9:40scenarios. So, if I’m signing in,
  204. 9:43I’ll have the main page of the
  205. 9:45service here, right, that appears after
  206. 9:48logging in. And here, I’ll have a
  207. 9:52page, like a success page should be
  208. 9:55there for me. Well, every time I ask
  209. 10:00someone to do something, like, say,
  210. 10:02enter a code, I need to give the person
  211. 10:06feedback that what they did is
  212. 10:08happening, that everything is fine.
  213. 10:12This thing might appear for a second,
  214. 10:15but I’m still including it so I can
  215. 10:19continue working. So, a question. Why
  216. 10:21in IT, anyway? The app should remember
  217. 10:23the user, right? That’s in case the
  218. 10:25user logs out of their profile, right?
  219. 10:28If they log out, well, we still design
  220. 10:30it from the very beginning, from an
  221. 10:32empty state, completely, when we have
  222. 10:35nothing. Well, I mean, ideally, when we
  223. 10:37design, we always design the most
  224. 10:40complete, the most full scenario there
  225. 10:42is, which is registration. And then,
  226. 10:45well, in this case it's registration,
  227. 10:47and then we trim off the unnecessary
  228. 10:49screens, and, like, sign-in is a
  229. 10:51stripped-down registration, social
  230. 10:53media authorization is also a
  231. 10:54stripped-down registration, because it
  232. 10:56has even fewer pages. Well, ultimately,
  233. 11:01I have a retro plugin that I bought for
  234. 11:0550 dollars and I will never part with
  235. 11:08it in my life. So I’ll quickly show
  236. 11:13you how it works. See, we have a
  237. 11:16passwordless setup here. I mean, if we
  238. 11:18had also added AIL—but I threw it out
  239. 11:21so we wouldn't be here until midnight
  240. 11:24—we would also have a "Forgot
  241. 11:26Password" format and, like, I don't
  242. 11:28know, maybe some things like "code not
  243. 11:31received" and so on. That is exactly
  244. 11:34what these CGM tricks are, which you
  245. 11:37will see in this new lecture that is
  246. 11:40available to you. Because, in essence,
  247. 11:44when we work with a CJM, I built you a
  248. 11:46direct scenario, several of them. And
  249. 11:49here is what can happen between these
  250. 11:53things, like, can something break here?
  251. 11:57Well, something went wrong. Well,
  252. 11:59unlikely, but, in principle, it's
  253. 12:00possible. Can something break right
  254. 12:03here? Can something break right here?
  255. 12:05Can something break right here? Like,
  256. 12:08you are looking for all these, well,
  257. 12:10kinds of problems. I mean, like a
  258. 12:13person signing in. If they have a
  259. 12:15password here, it means they forgot the
  260. 12:17password, or maybe they forgot their
  261. 12:18email, or maybe they forgot something
  262. 12:20else. Well, the services, depending on
  263. 12:23how old they are, try to cover as many
  264. 12:26scenarios as possible. Yeah. Then next.
  265. 12:30There is onboarding here, but since I
  266. 12:32don't have the functionality yet, I
  267. 12:34can't design the onboarding. I mean,
  268. 12:37onboarding is designed as training for
  269. 12:39what already exists, and I don't have
  270. 12:42it yet. Therefore, I will put
  271. 12:44onboarding aside for now. Well, I'll
  272. 12:46draw, I don't know, some little clock
  273. 12:48here so that I can look at it later.
  274. 12:51Yeah. Let's move on. What do we have
  275. 12:54here? Let's read. Creating various
  276. 12:57accounts, recording expenses, income,
  277. 12:59creating categories, the ability to
  278. 13:01convert currencies, creating tags,
  279. 13:03enabling or disabling public lists, and
  280. 13:06so on. That is already some kind of
  281. 13:08local function. Okay, entering
  282. 13:10operations, switching tabs between main
  283. 13:13operations. Okay, income, expense,
  284. 13:15debts, exchange. Income, expense, debts
  285. 13:17, exchange. I understand that this is
  286. 13:19the main list of operations. I'll read
  287. 13:21through everything that's here right
  288. 13:22now. Okay, bank push notifications. The
  289. 13:24ability to manage a family budget,
  290. 13:26adding a user. Loans, these are like
  291. 13:29accounts. Store receipts–that’s a
  292. 13:31functionality. Receipts, lists with
  293. 13:34totals. Hmm, oh, I see. It's like going
  294. 13:38to the store, tracking investments,
  295. 13:40portfolios. Please, let's do without
  296. 13:42that for now. Masha handles that at
  297. 13:44work. That is a terrifically huge topic
  298. 13:47. That would essentially be another
  299. 13:49large service. Everything there is just
  300. 13:52very complicated. So, let's start with
  301. 13:56this big thing here. Oh, they didn't
  302. 13:59pick an easy service to build. Well,
  303. 14:01let's dig into it. Let's start with the
  304. 14:03fact that we need information
  305. 14:05architecture here. We don't really have
  306. 14:07it in the project right now. Well, it
  307. 14:09exists in this form, but not as a tree.
  308. 14:12Let's try to figure out what we need.
  309. 14:17So, we have some kind of accounts. We
  310. 14:20have, uh, income, expenses. I
  311. 14:24understand that these are operation
  312. 14:26types. I mean, it's some operation that
  313. 14:29you perform. There’s an expense
  314. 14:32category. Categories of expenses. I
  315. 14:37take it that an expense category
  316. 14:38relates to the operation type. Meaning,
  317. 14:41I spent something and assign it to a
  318. 14:44category. Then currency conversion, a
  319. 14:47confusing thing. For now, you can also
  320. 14:51assign a tag here. Account publicity.
  321. 14:56Accounts should be public. There. Well,
  322. 14:59to simplify things for myself, I need
  323. 15:02to group, uh, based on information
  324. 15:05architecture, what objects I actually
  325. 15:08have and what attributes these objects
  326. 15:12have. And I'm trying to figure out
  327. 15:14currency conversion. What exactly are
  328. 15:16currencies? I understand that an
  329. 15:18operation also has a currency. And
  330. 15:20currency can be converted, which isn't
  331. 15:23very important for us right now–all
  332. 15:25these actions. We will work on them
  333. 15:28separately. I'll show you what we're
  334. 15:31doing with them. So, this can be
  335. 15:33created. This can be created. I'm
  336. 15:35writing down everything I see right
  337. 15:37away. Enable/disable publicity for
  338. 15:39accounts and lists. What kind of lists?
  339. 15:42I don't understand what these lists are
  340. 15:43. For now, it seems we've written down
  341. 15:47everything here, except for lists or
  342. 15:50checklists for groceries. I found them,
  343. 15:53but haven't used them yet. Well,
  344. 15:55someone who uses them, let us know
  345. 15:58later. Is it okay or not? So, you see,
  346. 16:01for my own and your convenience, I’m
  347. 16:04marking the possible actions in gray.
  348. 16:08Then let's read on. Here are the
  349. 16:10operations. Well, here it is. Meaning,
  350. 16:13I can also create an operation directly
  351. 16:16. Well, essentially, I’m creating it
  352. 16:19and entering all this data. Okay,
  353. 16:23switching between main operations using
  354. 16:26tabs. Income, expense, debts, currency
  355. 16:30exchange, transfers. Now we’ll figure
  356. 16:33out what that is. You see, here in the
  357. 16:36CGM, you often start getting some
  358. 16:39specifics related to the interfaces. At
  359. 16:42the very least, there are tabs here—
  360. 16:45that’s the author’s intent—that
  361. 16:48switch between the main operations. So,
  362. 16:52income, expense, debts, currency
  363. 16:54exchange, transfers. Let's read in
  364. 16:55detail what these are. Uh-huh. Expenses
  365. 16:59. This is basically a ready-made spec
  366. 17:02for designing these things. Right,
  367. 17:06let's try to sketch this out. So we
  368. 17:10have a main page, and we have five main
  369. 17:14entities that people use. Here, when we
  370. 17:17have a deep nesting of various entities
  371. 17:21, you can see there’s a transaction
  372. 17:24type—or rather, I’ll write it like
  373. 17:27this. This is an operation. The
  374. 17:30operation has a type, namely income or
  375. 17:35expense. Well, there is also income,
  376. 17:38expense, and there is also debt. It’s
  377. 17:41not clear yet what a debt is. Is it an
  378. 17:43operation or an account? Because, you
  379. 17:45see, there are accounts. So it seems to
  380. 17:49me that a debt is an account that we
  381. 17:51perform operations on. Meaning we
  382. 17:55either borrow, or we lend. Okay, fine.
  383. 18:00Where should I put these debts? I’ll
  384. 18:02figure it out now. Type: expense,
  385. 18:05income. Accounts also have types,
  386. 18:08including a debt type, and there are
  387. 18:11probably other types for sure. Okay,
  388. 18:14currency exchange, selling, buying,
  389. 18:17selecting currency, choosing a storage
  390. 18:19location, tags, comments. So, I
  391. 18:22understand that the currency belongs to
  392. 18:25the account. Well, it's clear, like,
  393. 18:33ruble, for example, I’m writing this
  394. 18:36for myself so I don't get confused
  395. 18:39later. Well, we’ll record all of this
  396. 18:41too. Choosing a storage location,
  397. 18:43transfer, entering an amount, selecting
  398. 18:45a currency. Anyway, for now, we have
  399. 18:48something like this. And we need to
  400. 18:51understand how people actually use
  401. 18:53these interfaces. Well, I suspect that
  402. 18:57these financial interfaces have a
  403. 19:00specific pattern in how they look. But
  404. 19:04since I won't be looking at anything—
  405. 19:06to make it harder for me and more
  406. 19:08interesting for you—I will improvise.
  407. 19:10Well, improvise, including how people
  408. 19:13use this stuff, because I don't have
  409. 19:15interview materials to rely on. But
  410. 19:18what is actually important to us? Well,
  411. 19:20what's important is the following.
  412. 19:23Whichever of these things people use
  413. 19:26most often should be at the top of our
  414. 19:30service's visual hierarchy. As I
  415. 19:34understand it, people spend money most
  416. 19:38often. I mean, they're constantly
  417. 19:41making expenses. That's why the
  418. 19:44expenses screen is first. Then income,
  419. 19:46then debts, then currency exchange, and
  420. 19:48transfers. Actually, they are probably
  421. 19:52arranged here in some sort of order of
  422. 19:55popularity. And I will create—if it's
  423. 19:59all about these five screens here—
  424. 20:01I'll create five screens with these
  425. 20:03names. Okay, this will be expenses,
  426. 20:06this will be income. I already want to
  427. 20:09start drawing, but I’m holding myself
  428. 20:11back because I want to outline the
  429. 20:13scope of work first. Expenses, debts,
  430. 20:16what else, exchange and transfers. Now,
  431. 20:19transfers. I don't really understand
  432. 20:21what that is. So, what else is missing
  433. 20:24here? I'll say right away what's
  434. 20:26missing: I'm writing it down:
  435. 20:28transaction history—well, history,
  436. 20:30yes, income history, expense history—
  437. 20:33there should be some transaction
  438. 20:35history everywhere. Well, at the very
  439. 20:37least, as a function. That just comes
  440. 20:40from the banking background. Okay, so
  441. 20:43let's assume we have these things:
  442. 20:45expenses, income, debts, exchange, and
  443. 20:47transfers. Let’s figure out which of
  444. 20:51these are separate entities. I suspect
  445. 20:54that expense and income are the same
  446. 20:57thing, like, they're just transactions.
  447. 21:00Debt is just an account. I mean, we
  448. 21:05have some types of accounts, and debt
  449. 21:07is just a common type of account. So,
  450. 21:12these are our transactions. But I don't
  451. 21:14understand what "exchange" is. Is it
  452. 21:16just some kind of service, or is it a
  453. 21:20history of operations related to
  454. 21:23changing currency? That, in short, is
  455. 21:26still unclear to me. Like, what is it
  456. 21:27exactly? Should it even be a separate
  457. 21:30tab, or should it be a filter somewhere
  458. 21:33inside this history? And I don't
  459. 21:36understand "transfers" yet either. Why
  460. 21:38are there commission amounts? Here
  461. 21:40there is a commission. Here there is no
  462. 21:42commission, even though there should be
  463. 21:43one for currency exchange. I don't
  464. 21:45understand what that is either. So, in
  465. 21:47order to design this, I need to learn
  466. 21:49more about what it is. So, that's why I
  467. 21:52won't be designing this just yet. I'll
  468. 21:54just, uh, sort of grey it out. Well,
  469. 21:57grey it out a little. Let’s work with
  470. 22:01what we have next. I mean, if there is
  471. 22:06a page with all the transactions,
  472. 22:09expenses, income, and so on, then there
  473. 22:13must be a page for a single transaction
  474. 22:16, right? Well, that’s just logical.
  475. 22:19So, a single transaction page must
  476. 22:21exist. And you see, exactly what Dasha
  477. 22:24wrote here—like the amount, currency,
  478. 22:28storage location, category, comments—
  479. 22:31all of this must be reflected on that
  480. 22:34page. If we have a transaction page and
  481. 22:38a page for all expenses, then there
  482. 22:40must also be a page that creates these
  483. 22:43transactions, right? Otherwise, where
  484. 22:46would they come from? That's it. And I
  485. 22:49usually write this creation part like
  486. 22:52this, because, well, we have a data
  487. 22:55entry pattern, right, when we create
  488. 22:57something. And editing is essentially
  489. 23:00changing the data that was entered. So
  490. 23:02this page will be practically identical
  491. 23:05, with the only difference being the
  492. 23:08header. Most likely, income is also a
  493. 23:11transaction, so they don’t need their
  494. 23:13own separate pages. But a debt is an
  495. 23:15account. And what will we do here? I
  496. 23:19think you can guess now, right, that if
  497. 23:22we have one account, then at least
  498. 23:24someone created it at some point,
  499. 23:27correct? If there is a debt account,
  500. 23:29then there is a "piggy bank" account,
  501. 23:31or some other account. And there is
  502. 23:34surely an account page. Well, it just
  503. 23:37follows from the logic. Well, like the
  504. 23:39existence of certain things in our
  505. 23:41project. Well, I won't touch the
  506. 23:43exchanges and transfers for now, I
  507. 23:44don't really want to. Let's see what
  508. 23:48else is here. Here's what isn't being
  509. 23:50mentioned. You know, when you talk to
  510. 23:53people in interviews, they usually
  511. 23:56don't tell you about things they take
  512. 24:00for granted. Nobody ever talks about
  513. 24:03registration in interviews because
  514. 24:05people just breeze through it and
  515. 24:08that's it. And they also always forget
  516. 24:11about the user profile. Where is our
  517. 24:13user profile? We don’t have a user
  518. 24:16profile, but if there is a user who
  519. 24:18uses the app, then their data must be
  520. 24:21stored somewhere. So we will make this
  521. 24:24thing: a user profile. If a person has
  522. 24:27a user profile, what is inside it? Well
  523. 24:30, probably their name, their contacts,
  524. 24:33that sort of thing. What else is
  525. 24:36supposed to be in there? Well, let's
  526. 24:38say, code methods. Hmm, if we have a
  527. 24:42rich service, it probably has, I don't
  528. 24:45know, well, you can look at Telegram,
  529. 24:47for example, one of the richest
  530. 24:49services. It has history, login info,
  531. 24:53in short, what else, which devices are
  532. 24:57currently connected, and much, much
  533. 25:00more. I always add two more things:
  534. 25:03logout and account deletion. People
  535. 25:06always forget them because they get
  536. 25:09used to the account. That's why you
  537. 25:11always need some kind of donor service.
  538. 25:13So you don't forget and it's easy for
  539. 25:15you to come up with features instead of
  540. 25:17pulling them out of thin air, you just
  541. 25:19go: "Aha, forgot this, this, this, and
  542. 25:21this." So you need some competitor
  543. 25:23service. Competitor analysis. That's
  544. 25:25why we usually do it before we start
  545. 25:27designing. I mean, you can build a CJM,
  546. 25:30but you still need a competitor
  547. 25:32analysis. Benchmarks, for instance. And
  548. 25:34what else is there? We make money on
  549. 25:37the service. We earn. That means we
  550. 25:40should have at least a subscription
  551. 25:43page. And you can immediately write
  552. 25:46down what's there: duration, cost, plan
  553. 25:49, lots of stuff, in short, things we
  554. 25:51tend to forget. Duration, cost, plan,
  555. 25:55plan switching, cancellation, payment,
  556. 25:58in short, something like that should be
  557. 26:02there. Oh, card linking, card updates.
  558. 26:07Anyway, you also need a benchmark here
  559. 26:09to list absolutely everything related
  560. 26:11to the subscription, you need to look
  561. 26:13for donors. And at a minimum, we have a
  562. 26:16page with, well, if there's a
  563. 26:17subscription, there are probably
  564. 26:19pricing plans. There are always legal
  565. 26:23documents, there's always support,
  566. 26:25contacts, like, something should be
  567. 26:27there. And for such services, there's
  568. 26:31likely a knowledge base too, though it
  569. 26:34might be in Zendesk, but I'll write it
  570. 26:37down anyway. Look, our screen flow is
  571. 26:40ready, even without the content. And
  572. 26:44the next thing we do is, well, we've
  573. 26:47listed everything that should be here,
  574. 26:51and you just go and find references for
  575. 26:55each of these screens, because there
  576. 26:58are usually dozens of different details
  577. 27:02on them, and so we don't forget them or
  578. 27:05invent them from scratch, we just draft
  579. 27:09this list. Well, let's, well, I won't
  580. 27:13go ahead and design this and that. I
  581. 27:15won't design this in detail right now
  582. 27:17because you can all do it yourselves by
  583. 27:19looking at Mobbin. Let's design
  584. 27:21something that doesn't exist yet. I
  585. 27:24mean, this part right here. To keep
  586. 27:27things clear, I'll move it aside for
  587. 27:30now. Alright. There. Right here. And
  588. 27:34I'll take this thing too. Okay. Let's
  589. 27:37start. By the way, I should label this
  590. 27:39as the main page. Hmm, we have accounts
  591. 27:43, we have transactions. We have
  592. 27:45accounts and transactions. I think,
  593. 27:49well, my personal take is that I open a
  594. 27:53budgeting app with two main goals: to
  595. 27:56see how much money I have and to log
  596. 28:00some expenses. I probably log expenses
  597. 28:04much more often, but the story about
  598. 28:06how much money I have, in which
  599. 28:08accounts, and what my financial status
  600. 28:10is, is probably just as important. So,
  601. 28:13for starters, I'd carve out an area
  602. 28:18that I'll consider a dashboard, or
  603. 28:22whatever you want to call it, that
  604. 28:27shows the account status. And, well,
  605. 28:32imagine for a moment that not a single
  606. 28:35personal finance service exists in the
  607. 28:38world—how would you even work in that
  608. 28:41scenario? I'll show you right now. So,
  609. 28:44imagine, right, that no personal
  610. 28:46finance service exists at all. You need
  611. 28:49to design a screen, something
  612. 28:50completely new. Then you think about
  613. 28:54what blocks this screen should consist
  614. 28:56of. The task is, for example, to show
  615. 29:00the account status here. What is the
  616. 29:02actual task? To show transaction
  617. 29:05history and the total amount spent over
  618. 29:09a period. I think that's what we mean
  619. 29:15by "expenses." So look, the task is to
  620. 29:19show account status. Let's brainstorm a
  621. 29:22bit in the chat—what could this even
  622. 29:25look like? I mean, what elements could
  623. 29:29be on the screen to show account status
  624. 29:32, and in which apps have you seen them?
  625. 29:36Please write in the chat. Mobile
  626. 29:38banking. Great. Banks consist of
  627. 29:41numbers. Maybe icons. Yes, exactly. So,
  628. 29:46look, this is what it means to have
  629. 29:48exposure to different types of apps.
  630. 29:52For instance, look at this: a list of
  631. 29:54tickers. You can use that as a
  632. 29:56reference for accounts. In short, Yahoo
  633. 30:00Finance, TradingView, Binance. So, if
  634. 30:03you're building a finance app, you can
  635. 30:06check out trading apps. And here you
  636. 30:08will have a bunch of different numbers,
  637. 30:11uh, charts, and some tables. Moreover,
  638. 30:14you see, it can also be sliced in a
  639. 30:18certain way. Now let's open their main,
  640. 30:21like, service to see how it looks. Well
  641. 30:23, there you go. And here you can, in
  642. 30:26short, peek at various ideas. For
  643. 30:29instance, they used to have this thing
  644. 30:31before, but now for some reason I don't
  645. 30:33see it. That’s switching accounts
  646. 30:36using a button at the top. I mean, here
  647. 30:39, for example, is adding a symbol via a
  648. 30:42pop-up window. In short, even if you
  649. 30:45don't really know how finance people do
  650. 30:48certain things, you can look at other
  651. 30:51financial services that these people
  652. 30:54clearly use, well, if you have some
  653. 30:57professional background, and see what
  654. 31:01is familiar to them. I mean, what kind
  655. 31:04of interfaces do they actually digest,
  656. 31:06you know? Because they might have
  657. 31:09everything much more—for some reason
  658. 31:11they really changed things here. There.
  659. 31:14So, in short, when you encounter an
  660. 31:17interface that you have never designed
  661. 31:20in your life, you break this interface
  662. 31:23down into tasks that you need to solve
  663. 31:27within a single screen, and you look
  664. 31:29for references for each task separately
  665. 31:33in thematic interfaces. Or, well, the
  666. 31:37coolest part: if, for example, I want
  667. 31:39to do something financial, but instead
  668. 31:41of peeking at finance, I peek at, say,
  669. 31:44medical interfaces, because they have
  670. 31:46the same cards, numbers, and tables.
  671. 31:49And you have to dig through your head,
  672. 31:51where you might have seen, I don't know
  673. 31:54, a lab results table, and it might fit
  674. 31:56here as a finance table. Essentially,
  675. 31:59what you need to do to make your brain
  676. 32:02work fast is to quickly grab different,
  677. 32:05well, pieces from different places via
  678. 32:08screenshots and just overlay them to
  679. 32:11see how they fit and to what extent
  680. 32:14they fit. So, absolutely any service
  681. 32:17that is out there can become a donor.
  682. 32:19There. Mm, that’s, like,
  683. 32:21theoretically how you can approach this
  684. 32:23. But if we approach it, for example,
  685. 32:28from hardcore drawing, just straight
  686. 32:31from hardcore drawing, then we will
  687. 32:33need our information architecture here
  688. 32:36so that we can draw at least something,
  689. 32:39if we, well, if we don't want to use
  690. 32:41references and have nothing to lean on.
  691. 32:45Here is what we have put together.
  692. 32:48Let's see. So we have these two things
  693. 32:51here: account and transactions. Let's
  694. 32:56start with the transactions, because
  695. 32:57there's just a whole bunch of stuff in
  696. 32:59these transactions. Right. And what are
  697. 33:02we going to do now? We are going to put
  698. 33:04together an information architecture
  699. 33:06and write down everything we've come up
  700. 33:08with on the screen in great detail. So,
  701. 33:11I'll put this here. I'll shrink it down
  702. 33:14so I have space to work with it. And
  703. 33:17now I need to fill this out as well as
  704. 33:19possible. Right. Well, I understand
  705. 33:22that this is exactly what I need here.
  706. 33:25This is everything I need. Okay, amount
  707. 33:28, currency. Currency is there, amount
  708. 33:31is missing. Amount, currency—
  709. 33:34currencies are there. Storage location.
  710. 33:37Storage location. Where to take the
  711. 33:38money from? I assume this is the
  712. 33:40account. I don't have the account here.
  713. 33:42Category is there, comment is missing.
  714. 33:46Tag is there, date is missing, probably
  715. 33:50time too.
  716. 33:52Photo of the receipt, scan, if there is
  717. 33:54a scan button. And, well, save, that's
  718. 33:58clear. That's the button, if it's there
  719. 34:01. Look, we have an information
  720. 34:02architecture. Now let's think about how
  721. 34:06many transactions it might be
  722. 34:08interesting for a person to see on a
  723. 34:11page, because the navigation pattern
  724. 34:14we'll use depends on that. What do you
  725. 34:17think? Write in the chat, how many
  726. 34:20transactions might a person need to see
  727. 34:23on one page? Like, 5, 10, 100 or so.
  728. 34:28Well, how many does he actually work
  729. 34:30with? Well, latest, not latest, I don't
  730. 34:32know. I mean, just imagine, right? So,
  731. 34:35you see, transactions. And another good
  732. 34:39question is, what period does the
  733. 34:42person work with? I mean, what period
  734. 34:46of history or transactions is he
  735. 34:48interested in? Today, this week, this
  736. 34:51month, this year, this quarter, or all
  737. 34:53time. Well, by the way, I don't know
  738. 34:56why you are writing 35. Do you find it
  739. 34:58convenient in your bank app when you
  740. 34:59log in and see only 3 to 5 transactions
  741. 35:01? I mean, it seems to me, especially
  742. 35:04since we are designing a desktop
  743. 35:05interface right now, don't forget, we
  744. 35:07have a lot of space. Well, I think so,
  745. 35:11yes, I think there are about ten types
  746. 35:13of operations, or five of them. There
  747. 35:16you go. Or five tabs, in short. By the
  748. 35:18way, we can set up the tabs right away
  749. 35:20because the project author really wants
  750. 35:23that. I'll make them right now as well.
  751. 35:25Five of them. Okay, let's assume that.
  752. 35:27You see, I've reserved a little bit of
  753. 35:29space for myself anyway for the future.
  754. 35:31So, okay. Well, let's say about 10
  755. 35:33transactions. Let's play a little more
  756. 35:37with design. If we have, I don't know,
  757. 35:41three to five objects on a page, what
  758. 35:43type of view should we choose to
  759. 35:46display them? What is the best way to
  760. 35:48draw these three to five objects on a
  761. 35:51page? Keep in mind, look at how many
  762. 35:54attributes we have here. Like, what is
  763. 35:57this, what is it exactly? What are we
  764. 35:59supposed to draw? Cards. Lena is right;
  765. 36:01if it's three to five, four, or even
  766. 36:04one, a card is the way to go—a card
  767. 36:06where we lay it all out beautifully.
  768. 36:09But what if there are 10? What would be
  769. 36:11the most convenient way to show that?
  770. 36:13There could be two options. A table.
  771. 36:15And what is the second option? Okay,
  772. 36:17I'm confusing you. The second option is
  773. 36:18cards with filters. I mean, if we have
  774. 36:21a lot of options, like 10, 20, 30, or
  775. 36:2340, we can still use cards, but with
  776. 36:25filters. And if we have a ton, we can
  777. 36:28use a table with filters. So remember,
  778. 36:32we start with the simplest way to
  779. 36:34represent information, which is just a
  780. 36:37list, like 1, 2, 3. Then, in that list,
  781. 36:43in those rows, we can have several
  782. 36:45different values. Then we realize we
  783. 36:49have too many values, so we make a
  784. 36:51table. If a table isn't enough, we
  785. 36:56split, say, 1,000 objects into five
  786. 36:59parts—that's 200 objects each—or 10
  787. 37:03parts if we can categorize them, like:
  788. 37:08tech expenses, food expenses, or
  789. 37:11something else—and then it's only
  790. 37:15100-200 transactions. So it's already
  791. 37:18simpler. Or we have 1,000 objects and
  792. 37:21we apply filters, for example,
  793. 37:24categories. Filters for tags, currency,
  794. 37:28amount, account, date, receipt
  795. 37:30availability, and type. In short, a
  796. 37:34bunch of filters at the top. We draw
  797. 37:35them right here. And please, a table
  798. 37:37can hold as many values as you want,
  799. 37:40even a million. I mean, the more values
  800. 37:44you have, the bulkier your filters and
  801. 37:47categories will become. So for that,
  802. 37:51you'll also have to add pagination at
  803. 37:53the bottom. For example, you show 100
  804. 37:57rows of filtered expenses on one page,
  805. 38:00right? Just imagine, even after
  806. 38:03filtering everything you possibly could
  807. 38:05, you still have 1,000 values left. So,
  808. 38:07we'll have to show them page by page,
  809. 38:09100 at a time, and load them in
  810. 38:11portions. And this, in essence, is your
  811. 38:14navigation work. Well, I mean, I
  812. 38:17imagine that, well, it seems to me that
  813. 38:20a table would be the most convenient
  814. 38:22thing. Now we need, uh, some sample
  815. 38:25data, roughly speaking. I mean, what is
  816. 38:29an operation type? What kind of words
  817. 38:32are those, anyway? So, we go and look:
  818. 38:35income, expense, say, I don't know, if
  819. 38:38it's a debt—that's an account; well,
  820. 38:40I think we have others...maybe, in
  821. 38:42short, exchange, or something else, I
  822. 38:44don't know, well, in short, some
  823. 38:46operation types—I won't go into
  824. 38:48detail right now—and we write them
  825. 38:50down for ourselves. Why do we write
  826. 38:53them down? To understand what kind of
  827. 38:56content is actually hidden behind this
  828. 39:00object, because there might be, say,
  829. 39:03super-long words here, or maybe there's
  830. 39:06an ID that's, I don't know, 16
  831. 39:09characters long. And I need to
  832. 39:13understand if a standard table might
  833. 39:16not work for me; maybe all this diverse
  834. 39:19information won't fit horizontally. So,
  835. 39:23I understand that an operation is
  836. 39:24income or expense. Then what else is
  837. 39:28there? Well, obviously, there's a "
  838. 39:30create" button at the end. Category. I
  839. 39:33gather that the category could be of
  840. 39:35any length at all. I don't know, let's
  841. 39:38write something long. "Culinary
  842. 39:41masterclasses," for example—I love
  843. 39:43going to culinary masterclasses, right?
  844. 39:46Like, I'll have to do something with
  845. 39:47them. So, we've sorted out the category
  846. 39:51. Tags. This is also interesting: can
  847. 39:53an operation have more than one
  848. 39:55category or not? Like, I'm pretty sure
  849. 39:58it doesn't. Tags: how many tags can
  850. 40:01there be, and how long can they be? I
  851. 40:05mean, I assume that tags could be of a
  852. 40:08decent size. Let me draw them now so
  853. 40:11it's clear that these are tags. Then,
  854. 40:14currency. Well, currency is just a
  855. 40:16symbol, so it doesn't need much space.
  856. 40:18Then what else? Well, here you could
  857. 40:21somehow convert it too. What size could
  858. 40:24the amount be? You see, my iconic fonts
  859. 40:27, like size 24, already don't fit the
  860. 40:30actions you can perform on an operation
  861. 40:33. Well, I think that for ordinary
  862. 40:35operations, the amounts—well, if we
  863. 40:37take even 10 million, that's more than
  864. 40:40enough; well, 99 million, like, I don't
  865. 40:42think there are many operations much
  866. 40:44larger than that. Well, there will be
  867. 40:46some margin left there. Then, account.
  868. 40:51I think this should actually be
  869. 40:52somewhere at the very beginning. Create
  870. 40:57another tag. Account. An account might
  871. 41:01also have some name. Well, as a rule,
  872. 41:05let's say, let's call it Tinkoff. I'll
  873. 41:09fold this up right away. Spoilers, yes,
  874. 41:11I'm going to have a two-level table.
  875. 41:13Okay, comment. That's also a question,
  876. 41:19like, depending on the system. For
  877. 41:21example, there are systems like the
  878. 41:24sanctions blocking tool I developed,
  879. 41:27where comments were very important.
  880. 41:30Basically, the comments were the most
  881. 41:33essential thing there. So here, as you
  882. 41:37can see, we probably don't have enough
  883. 41:41room for everything we want to add. in
  884. 41:46one table, because the font size is
  885. 41:48already 18. So, it will likely become
  886. 41:5216 for desktop. And I'm afraid it won't
  887. 41:56fit. So I need to decide: if everything
  888. 42:01doesn't fit, I'll have to hide some
  889. 42:05things inside or find a workaround. For
  890. 42:10instance, the amount and currency. Look
  891. 42:13, I can save some space here. There.
  892. 42:15And there are plenty of such techniques
  893. 42:18in table layout. Maybe the comments
  894. 42:21will be inside, or maybe they'll pop up
  895. 42:24on an icon. Okay, date and time too. We
  896. 42:28can just write it all in one line. Here
  897. 42:32, for example, 09/16/24. Note, by the
  898. 42:38way, that other countries write this
  899. 42:40differently. Like this. As you can see,
  900. 42:42it's already wrapping to two lines
  901. 42:44because of the tags. I can collapse
  902. 42:46this part here too. Well, it seems to
  903. 42:51fit for now. There. And a receipt too.
  904. 42:54I'll show an icon as well. On hover. It
  905. 42:59will all work for me. Okay. So look, I
  906. 43:05essentially already have a table. What
  907. 43:09can I do? I can do an expensive
  908. 43:13solution. By the way, I'll show you an
  909. 43:15expensive and a cheap table filter
  910. 43:16solution. You might have seen such
  911. 43:19filters in Google Sheets or Kontur.
  912. 43:22Meaning, I click here, a window opens,
  913. 43:27and I choose which tags to include. And
  914. 43:32then they appear here, like, say, it
  915. 43:34shows "three". And these items get
  916. 43:37filtered. These are the expensive
  917. 43:39filters, basically, because they
  918. 43:40require building a separate component.
  919. 43:42But if you don't have such a component,
  920. 43:44you can make cheap filters. That is,
  921. 43:47you just take and duplicate them right
  922. 43:50here at the top. Well, literally all of
  923. 43:54them, in short, that you need. Just
  924. 43:59seriously, don't worry about it. Like,
  925. 44:00here there will be a type. Maybe, if
  926. 44:03there are two of them, that's easy.
  927. 44:06Date. That's two. Well, this is, in
  928. 44:10short, a range, the count is the same.
  929. 44:12Category, a drop-down list. Tag, also a
  930. 44:15drop-down list. Plus, there should be a
  931. 44:19button there too. Well, by the way,
  932. 44:21right here there could be a "create"
  933. 44:23button like this. Both "create tag,"
  934. 44:26both "add comment," both "add check."
  935. 44:35Well, you get it, right? Like, you need
  936. 44:37to bake these things in right away,
  937. 44:38because we have them in our information
  938. 44:40architecture, which means we need to
  939. 44:44make them actions. That is, you can
  940. 44:47have buttons here, or maybe icons, like
  941. 44:52you come up with some kind of exchange,
  942. 44:58conversion, or something else. In short
  943. 45:00, you can use buttons, or you can write
  944. 45:02the word "actions." And with an
  945. 45:05operation, some word, a drop-down list,
  946. 45:09and essentially an action there. I mean
  947. 45:12, all these things I'm writing down,
  948. 45:14it's just, well, all of this will open
  949. 45:16up for you in your references. That is,
  950. 45:19if you're going to work with tables,
  951. 45:21you need a reference with tables. And
  952. 45:23you can draw some ideas for yourself
  953. 45:25from these things. Okay. Ah, well, here
  954. 45:27, in short, are the filters. There must
  955. 45:30be an "apply" button here, and that's
  956. 45:33it. Well, voilà, my dear, it looks
  957. 45:40like I've designed a wireframe. There.
  958. 45:43Well, it's clear that this should be
  959. 45:45more compact. Perhaps the font should
  960. 45:48be small here, like a thirteen, and
  961. 45:50there should be pagination here because
  962. 45:52there will be many pages. I really like
  963. 45:56, I mean, I like doing this quickly,
  964. 45:58because look, when I work with
  965. 46:01wireframes, my...well, the difficulty
  966. 46:03with design is that you have to use two
  967. 46:06areas of the brain. The one responsible
  968. 46:09for drawing and detailing is the
  969. 46:11creative half, the left hemisphere, I
  970. 46:14think. The one responsible for coming
  971. 46:16up with ideas and planning is the right
  972. 46:18half. It's harder to strain that one.
  973. 46:19Well, at least for me, it's easy to
  974. 46:21draw. It's very hard for me, in short.
  975. 46:23To sit and write out these properties,
  976. 46:25all of this, in short, just so I don't
  977. 46:27miss anything. I don't miss a single
  978. 46:29button, a single filter, a single
  979. 46:31window here. By the way, design the
  980. 46:32windows you need right away too, so you
  981. 46:34don't forget. There. And when you
  982. 46:37design as quickly and dirtily as this,
  983. 46:39first of all, everyone already
  984. 46:41understands this. The more detailed
  985. 46:43your dirty prototype with windows and
  986. 46:45everything else is, the easier it will
  987. 46:47be to communicate with managers,
  988. 46:48developers, and others. This is already
  989. 46:50a sufficiently low level of abstraction
  990. 46:52. Essentially, everything that is
  991. 46:53needed is already drawn here. There. Uh
  992. 46:55, well, even the create tags and all
  993. 46:57that other stuff. We just forgot to
  994. 46:59draw the perk. Also, I forgot to do
  995. 47:02this, yes, that we have this tab
  996. 47:04enabled. Well, there you go. And,
  997. 47:07basically, I advise you to work like
  998. 47:09this if you have a complex service that
  999. 47:12requires wireframing, well, that is, it
  1000. 47:14requires wireframing, huge information
  1001. 47:16architecture, tons of things, tons of
  1002. 47:19functions, and lots of small iterations
  1003. 47:21. Like adding a tag, creating a tag.
  1004. 47:24All of this needs to be done together.
  1005. 47:26Make a very detailed wireframe and make
  1006. 47:28sure that you didn't forget anything
  1007. 47:30here. Go show it to the product manager
  1008. 47:32, go to the developers, testers, maybe
  1009. 47:34they'll suggest something to you. Bring
  1010. 47:37it to a state where everything is here
  1011. 47:39to the maximum, every element that you
  1012. 47:42need. And only then, when you feel that
  1013. 47:45, well, the wireframe is okay, sit down
  1014. 47:47and draw. Put on a movie, music, and
  1015. 47:50sit there doing the UI. In short, just
  1016. 47:52draw. Because if you didn't do it here
  1017. 47:55right away and started obsessing over
  1018. 47:57the UI, firstly, you'd forget half of
  1019. 48:00these things, and secondly, you'd spend
  1020. 48:02twice as much time, because drawing—
  1021. 48:05well, if you messed something up while
  1022. 48:08drawing, you then have to move
  1023. 48:10everything again, redo all the margins,
  1024. 48:12and so on. So it's better to work out
  1025. 48:16this screen as well as possible. So,
  1026. 48:19let's finish designing this thing and
  1027. 48:21go look at the work. Task: show the
  1028. 48:24account status. Well, I think we need
  1029. 48:26an account and the account's
  1030. 48:28information architecture here. What
  1031. 48:30does it have? Well, publicity. I don't
  1032. 48:33know, like, what that is or how it
  1033. 48:35works. Well, let's keep it. That there
  1034. 48:37should be publicity. What is publicity?
  1035. 48:40Probably some icon, right, that it's
  1036. 48:43public and that can be toggled on or
  1037. 48:46off. And it must have a type. I think
  1038. 48:50it has a name and it has a currency.
  1039. 48:54And I think it also has a balance,
  1040. 48:55which is probably even more important
  1041. 48:57than the name. Well, we'll write the
  1042. 49:00maximum here too right away. Well,
  1043. 49:02that's actually quite a lot. Well,
  1044. 49:03whatever. Let's assume. Like this. Like
  1045. 49:05this. Name, amount. Mm. Let's have some
  1046. 49:11type and currency here. Well, you get
  1047. 49:15it, right? Also just filled in. Maybe
  1048. 49:19we have some kind of button here to
  1049. 49:23switch currencies. That's very
  1050. 49:25convenient. By the way, financial
  1051. 49:26services often let you see how much
  1052. 49:28that is in dollars, euros, and so on,
  1053. 49:29at the current rate. Here’s the
  1054. 49:32privacy toggle, which you can turn on
  1055. 49:35or off. Well, I think I’ve wireframed
  1056. 49:38everything. And we can have a number of
  1057. 49:41these accounts, right? We can show the
  1058. 49:44status of these accounts. And what else
  1059. 49:46should be here for them? Well, the
  1060. 49:48personal account area, like, myself.
  1061. 49:51And there should be some other thing
  1062. 49:54here, like, create another account,
  1063. 49:56right? Well, and something else, that's
  1064. 49:59it. And so, in short, you’ve
  1065. 50:01wireframed this one screen. I'm just
  1066. 50:03working according to Dofeyev, you see?
  1067. 50:05And my next task is: draw this screen,
  1068. 50:07then draw this screen, then draw this
  1069. 50:10screen. And when you're asked to
  1070. 50:13estimate deadlines, you measure the
  1071. 50:15complexity of one screen and see: "Okay
  1072. 50:18, I spent 2 days on this complex screen
  1073. 50:21, and this one I designed in half a day
  1074. 50:24." And they ask you: "How long until
  1075. 50:26the work is done?" You count them like
  1076. 50:28this: 1, 2, 3, 4. You assign them a
  1077. 50:30complexity. Six complex ones, three
  1078. 50:33simple ones. And you're like, six times
  1079. 50:36two and three times half a day, like
  1080. 50:38twelve days. So you say, well, about a
  1081. 50:41week and a half, 10 days. And that will
  1082. 50:43be true. Well, more or less close to
  1083. 50:45the truth, because you already, well,
  1084. 50:47like, you have a list of screens. If
  1085. 50:49you had started drawing this
  1086. 50:50elaborately from the start like
  1087. 50:52intricate Chinese calligraphy, your
  1088. 50:54service would never have been finished.
  1089. 50:57But in product development, look, I
  1090. 51:00spent 20 minutes making this
  1091. 51:02placeholder screen flow, you understand
  1092. 51:04? It's already ready in some form. If
  1093. 51:07I’m asked: "Show me what you’ve
  1094. 51:09done." I'll say: "I designed this
  1095. 51:11layout in 20 minutes." If they come to
  1096. 51:14me in the evening and say, what have
  1097. 51:16you done, I'll say: "I’ve sketched
  1098. 51:17out this level of detail." It’s
  1099. 51:19better to go and sketch out this level
  1100. 51:22of detail for all screens, then go show
  1101. 51:25it to the manager, and only then sit
  1102. 51:27down and draw them one by one. And when
  1103. 51:30you're doing the UI, they'll ask for
  1104. 51:31deadlines again, and you'll say: "Well,
  1105. 51:33you measure it, like a simple screen
  1106. 51:35takes me, say, a day to design, and a
  1107. 51:36complex one takes 3 days." And that's
  1108. 51:39it. And you'll calculate it the same
  1109. 51:40way. That’s why someone in the chat
  1110. 51:42was just asking about deadlines. I
  1111. 51:43don't remember which one. There you go.
  1112. 51:44But, but that’s the mechanic.

About this transcript

This page contains the full transcript of Как построить cкринфлоу. Как превратить CJM в вайрфреймы. Зачем вообще нужны вайрфреймы? by Артур Кузьмин • Formfactor , generated from the public captions YouTube serves with the video. The transcript has 7,430 words across 1,112 segments, with the original timestamps preserved so you can click any line to jump to that moment in the embedded player.

What you can do with it

Use the transcript to take notes, quote the speaker, build a study guide, generate a summary with ChatGPT or Claude via the YouTube Summary tool, or export it as a timed subtitle file with YouTube to SRT. You can also re-open it in the transcriber to choose a caption track available on the video.

Free YouTube transcript tool

YouTube2Text is a free YouTube transcript generator — no signup, no daily limit. Paste any YouTube link and get the full transcript instantly, with timestamps, click-to-jump, caption language selection, AI prompts for ChatGPT, Claude, and Gemini, and exports to TXT, SRT, VTT, or Markdown.