Tanuj Bisht

@joshpuckett Monet also painted ~30 canvases of haystack for one whole year between 1890-1891. :) youtu.be/ww_lmtMpfqE?si…

Picasso painted the same view 9 times during a one week pause from a major project and you think you’re iterating enough?

@oykun @stripe

designers, name 1 company you'd take a pay cut to design for. 👀

day 3 — add a sheet with a “+” button + sheet vs fullScreenCover: .sheet slides up partially and lets users swipe down to dismiss, no close button needed, the affordance is built in. .fullScreenCover takes over the entire screen and removes that swipe gesture, making an explicit close button mandatory. the difference is not only visual, but it's semantic aswell. sheet is more like “temporary overlay, you can leave anytime.” full screen cover is more like “you are now in a new context, here is the exit.” in specific app content such as fintech, full screen covers belong only in flows that require full attention like onboarding, KYC, payment confirmation. Using one for a simple add form is over communicating urgency. The right pattern communicates the right weight. also, iOS modal navigation follows a semantic grammar: left means back or cancel, right means confirm or save. breaking this pattern creates confusion users feel but can't articulate but placement follows context, not a fixed rule. forms use “Cancel/Done” with left/right semantics because the user is making a decision. Informational sheets use a single X top-right because there's no decision but just exit. applying “Cancel/Done” grammar to a view-only sheet adds false weight to a simple dismissal. for apps like fintech: transaction detail sheets, rate cards, and info overlays should use “X”. payment flows and form sheets should use “Cancel + Done.”

also for the navigationstack+push to detail, gesture conflicts reveal the cost of implicit tap targets. what i designed: a card that navigates on tap and toggles completion on tap, same target, two jobs. what happened: onTapGesture intercepted all taps before NavigationLink could respond. tapping toggled the card but never navigated. dragging navigated because drag bypasses onTapGesture. there was silent conflict, no error, just broken behavior. fix: replaced full-card tap with an explicit checkmark Button inside the card. two distinct hit targets, row navigates, circle toggles. not for me: never assign two behaviors to one tap target. fintech list rows with inline actions (star, flag, mark paid) need explicit separate hit targets, not a single gesture doing double duty. figma prototypes hide this problem and real iOS surfaces it immediately

i wanted better at prototyping mobile interactions at actual codebase level for better control which has been challenging in figma + was curious to learn @appleswiftui. prompted @claudeai to design a specific "SwiftUI learning plan of 4-6 wks" with the goal "sharper interaction design+better understanding of a platform+handoff".

last week felt like collecting infinity stones. as a product designer, i'd spend any day as a fly on the wall in the design meetings of @stripe , @cursor_ai , @Lovable, or @clerk . last week, i got to briefly speak with the people running those rooms. two events in SF brought them all into the same orbit: → the new standard — @raycast × @cursor_ai × @vercel → @stripe Sessions 2026 Tthe people i got to meet: • Katie Dill (@lil_dill) — head of design, Stripe • Ryo Lyu (@ryolu_) — head of design, Cursor • Drew Wilson (@drewwilson) — founder, @OpacityHQ | prev.-head of design, Clerk • Nad Chistie (@nadonomy) — head of design, Lovable all too kind to hear me babble. some of it felt genuinely serendipitous. these are the rooms I want to keep being in where decisions like these get made. p.s. Drew is going to change the handoff paradigm between design and engineering. get on @OpacityHQ wish-list. i'm really excited for this one.

7/ Was already a big week in SF but these two talks are going to stay with me for a while and a got to week. meeting with some good amazing people.

3/ second: "economists on ai: labor markets and structural shifts" economists are finally talking about ai in ways that feel honest. three things i'm still thinking about: → the first wave of displacement is already here — it's just hitting freelancers first. up to 97% cost savings for companies switching from platforms like upwork to ai. no policy covers these workers. → the real structural shift isn't about the tools. it's about which organizations are willing to redesign how they work. that's where the employment gap will actually show up. → young workers are in the hardest spot. high interest rates already cut junior hiring. ai is now shrinking entry-level task demand. freelancing, the usual fallback is shrinking too. the productivity numbers look fine on paper. the real story is happening underneath them.

1/ @stripe Sessions 2026. Two talks I can't stop thinking about. 🧵

@monali_dambre tanujbisht.com love to chat. thanks.

Finding great designers is harder than it should be right now. If you care deeply about craft and are exploring opportunities, share your portfolio below. A few really good, well funded startups are hiring designer rn.

@rudrank Can you share the link to the SwiftUI SJ event? I would love attend it.

I know a lot already leave by 11th, and there is another event in San Jose that SwiftUI folks would love to go to

I am slowing down on approving the requests because it will be trouble if all show up 😆