20241010

https://developer.apple.com/videos/play/wwdc2023/10156/?time=1200

• Animatable vs. Animation. Animatable is the data being animated, and Animation is the animation function used for that data.
• SwiftUI animation lifecycle: SwiftUI tracks the derived values of a view. When those derived values (or dependencies) change, then the View is invalidated and re-computed. Animations are part of the View, so they are invalidated and elements are re-animated when the View is recomputed.
  • is SwiftUI smart enough to not re-animate the view when the dependency that it animates isn’t updated?
• The Animatable protocol just requires a read-write vector
  • why a vector? Vector operations make sense. Each component likely maps to a feature or aspect of the thing you’re animating, and you want operations for each feature to only pertain to itself. Plus you probably want to preserve the relative magnitudes of each feature.
• The CustomAnimation protocol requires an animate function and two optional functions: shouldMerge and velocity. The latter two are for when animations are interrupted.

Some other videos that I want to watch:

https://developer.apple.com/videos/play/tech-talks/10855

https://developer.apple.com/videos/play/wwdc2023/10160

https://developer.apple.com/videos/play/wwdc2022/110381/

Man Apple is so great lol.

20241008

Some notes on Linear onboarding

I really like the big ass Continue button. It’s bigger than you think it should be but it really does feel right and it reduces mental latency. The button’s background also doesn’t become visible until you hover over it, which I thought was an interesting decision.

The alternative is that you have a solid button background (like you do in the earlier onboarding screens). A bigger, more noticeable button is more distracting, but I feel that the same principle would apply for the Command+K screen.

Also, the cursor doesn’t become a pointer finger when you hover over the button. Not sure why ; the pointer finger is a useful affordance.

The keyboard shortcut buttons are longer than they are wide; which is in contrast to Raycast:

I think it’s probably a matter of preference.

The command menu is wary of context; it knows that you are inside of a to-do.

Also small thing to note is that the horizontal margins of the action items is quite thin. Everything has the same left-padding, including the icons.

20241006

Retain cycles, reference counting

econ 13.mov