Video yükleniyor...
Video Yüklenemedi
Ok, back again with another Fizzy in-development video. This time I go over two things: 1. Some subtle, but meaningful, UI updates that really dial things in. I love little tweaks like this. Small bits of work that lead to outsized experience gains. We use color to help you... show more
23,696 görüntüleme • 1 yıl önce •via X (Twitter)
11 Yorum

Ah and I share a couple examples of how you can use the Fizzy Do bar at the bottom to quickly jump around. There's a lot more hidden inside that bar — will share more on this in a future video.

⌨️ 2AM debugging session: Your code won't compile, Stack Overflow is your best friend, and your Kaiser 4 is the only one who understands... Every developer's late-night reality: 💻 "One more bug fix" turned into sunrise ☕ Coffee cup collection growing 🐛 That bug that just won't die Kaiser 4 speaks fluent Python: 🌟 4D lumbar support for those debugging postures ✨ Perfect height for multiple monitors 💫 Recline mode for code compilation breaks Because good code comes from comfortable devs! ⚡️ Debug in comfort: #AndaSeat #DevLife #CodingLife #ProgrammerSetup #gaming #gamingchair

Lovely work on the visual weight. Also that notification menu animation is so nice! 🤌 So many times the more direct approach is more metadata. But what if you can solve metadata without added text. Now, I'm curious how these screens look on mobile.

Thanks. And yes, trying to let color, space, and texture convey information without having to explicitly call things out. Once you develop an intuition for it, it communicates so much more with far less effort.

That spring animation when you fan open the notifications stack is real nice. Great example of adding a tiny element of delight to something that doesn't need it, but ultimately benefits greatly from it. Huge fan of the design work y'all do.

Thanks Adam. Dialing it in!

Just popping by to say that I love how you guys continue to build and launch like it's your first time. It's refreshing.

Thanks Josh. It’s always the first time!

Ooo I wonder what AR::Tenanted is? 👀

I like a lot of the concepts in here. We need more "different" ideas when it comes to todo management so I'm excited to see how this continues to evolve. I do feel this suffers from a common problem though, it's a bit too focused on a manager sitting in an app and watching engineers. Understandably, most of the people that build these apps are managers not engineers on the ground floor so they naturally gravitate that direction. But comparing this to say linear or jira, from a management perspective, is it really doing anything different? You can run reports in those to get your daily logs just the same. An engineer can open a ticket to see if it's moved, or use a kanban board. I'd love to see some new takes when it comes to helping engineers organize their own "sub-schedules" underneath the top level cycle planning. After planning, let engineers break those larger tasks into 1 day or smaller subtasks, then assign them to specific days. This forces them to think through the actionable work better and set goals for themselves. Then provide a page where the engineer can look at what they expect to get done each day. Maybe a kanban style with a "today" "tomorrow" and a "done" column. If a day goes sideways and they get behind, make it easy for them to "move" all the tickets forward a day. This lets them manage their own work, while also giving clear levers to notify a manager that timelines may change. But the key thing I'd love to see is starting at the engineer, encouraging them to manage their own schedule and goals. It's something that just feels lacking in all the current issue tracking softwares I've tried.

This is definitely not a tool for managers to sit around and watch. This is not a reporting product. There's nothing to generate. This is for people doing the work. Through and through.

