I provide it in that price range upon PPP coupon request. Lots of people have gotten it that way. People fill out a request here: tonyalicea.dev/courses/understanding-react-ppp/ I'll note that even as a premium course, I've still priced it well below what other premium courses outside of Udemy go for.

Interesting! TBH, I don't have Flutter/Dart experience. I try not to teach things I don't have practical experience with.

I had my reasons for making it premium, but if financials is an issue for folks you can request a PPP coupon: tonyalicea.dev/courses/understanding-react-ppp/

indeed. 100 or 150 $ is a lot. He would earn much less per course, but would have many more students.

@@adriantepes-qu8wm You can request a PPP coupon here, if you need: tonyalicea.dev/courses/understanding-react-ppp/ Lots have!

I love Vue!

I had my reasons for making it premium, but if financials is an issue for folks you can request a PPP coupon: tonyalicea.dev/courses/understanding-react-ppp/

Hi. may i know how you got a job?

I haven't taken the course yet though

@@henryogbogu3499 I was looking for a job like everyone else But the fact that I knew how to program properly got me the job

Already did, it's on Udemy!

Thanks so much!

No. “Pages and modals” is not the choice. The book gets into a lot more detail of course, but you’ve misunderstood. We are talking about user flows, cognitive load, a way of diagramming user flows, metrics to make choices, a matrix based on those metrics to make choices, wrapped in a way to categorize your workflows (which can get large) so you can use the decision matrix. We go through the metrics (frequency of use and complexity), how to measure them, and the rules for which results should be normalized or denormalized. I’ve taught and implemented this technique for years. BTW, pages and modals are *both* considered “screens” in a workflow here as they are equivalent from a cognitive load perspective. A workflow is the series of actions from beginning to end for any task. Normalization is about whether you stay on one “screen” or multiple as the user traverses those actions. That’s the choice. Hope that helps clarify for you!

Thanks so much! I hope the content is helpful! 🙂

Awesome! And yes Figma is terrific for considering normalized vs. denormalized workflows.

Awesome thanks so much! I am planning on more!

Thanks! The book is the culmination of 25 years of work. I'm so happy to get it out there and hope folks find the technique helpful.

Not sure what you mean here? Like I said I’ve been using this technique for 20 years, so first used with older languages but not dependent on any particular tech. Thanks for subscribing! I’m using a 3rd party form so no control over their normalization. 😄

@@TonyAlicea what I meant is that it goes against everything we’ve been trying to do with JavaScript for a long time now: a Single-Page-Application feel (SPA). Your technique is more of a classic website feel. We’ve been doing this forever you just tokenized it, put a name on it, isn’t it? Hope there’s more to it! Thing is with JavaScript Routers we might have the best of both worlds, the website simplicity and the SPA performance especially with not reloading the whole page and asynchronous loading of needed JS and other static resources like you mention in your video. Is it just for dangerous workflows tho? I can’t wait to see what you recommend for linking something, small text area that you can hide/show like Gmail, tabs-like changing view, etc…

In the book we get into when to denormalize (keep things all on one screen) and when to normalize (separate across screens). Various examples and concrete recommendations. The decision on whether to normalize or not has to do with frequency of use and complexity. I don't agree on your SPA/classic web point: the point of the SPA wasn't to keep everything on one page but to avoid page refreshes. You can normalize onto different screens in a SPA, opening different routes, and I don't think that goes against SPAs. This is a usability consideration: sometimes you need to reduce the user's cognitive load. Hope that makes sense!

It occurred to me part of the confusion may be the word “page”. I mean that from the user’s perspective. A “page” corresponds to a route in a SPA.

@@TonyAlicea got it 🙏. Would have been nice if the video showed one example of each: so when to keep all in one screen too. I’m gonna buy the video course for sure it’s interesting. From guessing: - when trivial, like liking a content on some social platform, it can be asynchronous request and state altering page elements - when dangerous, like send email reminder to a huge number of people, it’s better on different screen to get confirmation