Rajan Dube
@rajanndube
Followers
551
Following
3K
Media
37
Statuses
628
Lead Product Designer @get_aspora • Prev. Founding designer @JarAppHQ • No-Code • Also life & bollywood among other things
India
Joined January 2021
hi, i’m Rajan. i design products. i mentor young design foks. i overthink no-code. and sometimes, i tweet. you’ll see more of that now.
2
0
37
designed a web3 landing page before web3 became a joke. some of my past work. the challenge: make blockchain feel approachable. most web3 designs scream "i'm complicated and you're not smart enough." my approach: > clear value proposition above fold > visuals that explain,
2
0
18
in the ai era, your biggest competitor isn't other products. it's how easy you make it to leave. here's why most products are dying while some are becoming irreplaceable: 1/7
2
1
9
in the ai era, your biggest competitor isn't other products. it's how easy you make it to leave. here's why most products are dying while some are becoming irreplaceable: 1/7
2
1
9
you won't become a great designer by taking more courses, learning new software, copying trending styles. you'll become great by doing, failing spectacularly, learning and repeating. curiosity + practice beats theory every time.
5
1
26
Never mind, Figured it out! It’s working
@figma plugin question Has anyone built a Figma plugin that needs backend authentication? How did you handle CORS? I want to avoid adding "null" to the allowed origins because it feels risky for backend security. For all the builders here, have you faced this problem? How did
0
0
5
you won't become a great designer by taking more courses, learning new software, copying trending styles. you'll become great by doing, failing spectacularly, learning and repeating. curiosity + practice beats theory every time.
5
1
26
make your product so intuitive, so seamless, so predictable that it becomes invisible.
the best technology is the one you DON'T notice. here's why designers keep getting this backwards (sorry not sorry :P) - if technology works well, we can ignore it most of the time. your best designs shouldn't draw constant attention to themselves unless necessary. think about
0
0
7
but designers love making things "pop." fancy animations. bold interactions. attention-grabbing elements. this is classic ego design vs. user design. technology should slip seamlessly into the user's daily routine. not force them to adapt to a new one. the moment users have to
1
0
0
the best technology is the one you DON'T notice. here's why designers keep getting this backwards (sorry not sorry :P) - if technology works well, we can ignore it most of the time. your best designs shouldn't draw constant attention to themselves unless necessary. think about
2
0
5
i design 10x faster than most designers. not because i'm more talented. because i started at startups where "launch yesterday" was the only deadline. speed isn't about cutting corners. it's about knowing which corners to cut. constraint breeds clarity. clarity breeds speed.
10
0
47
if you are building, you need to understand the stories people tell here's probably WHY your feature list isn't connecting: people don't buy products. they buy better versions of their stories. "i'm organized" (@NotionHQ ) "i'm creative" (@figma ) "i'm connected" (@instagram
2
1
11
user interviews are lying to you. here is exactly WHY-
you NEED to know that behavior is best understood through observation 🧵 here's why user interviews are lying to you: 1/7
0
0
5
stop asking users what they want. start observing what they actually do. behaviour reveals truth. words reveal intentions. design for the truth. 7/7
0
0
1
the best designers are anthropologists. they observe: > workarounds users create > steps users skip > features users ignore > hacks users build then they formalise those behaviours into the product. 6/7
1
0
1
how to design for behaviour: > watch users in their natural environment > track actual usage patterns > identify friction in the journey > design for shortcuts they're already taking 5/7
1
0
1
real example: users said: "we want more customisation options" we observed: 90% never changed default settings the insight: they want the feeling of control, not actual control. we designed for the behaviour, not the request. 4/7
1
0
1