Buland Khan’s Post

Whatever niche you find yourself in, things are probably constantly changing. Being seen as a go-to source means your voice doesn’t just echo in the void - it influences. When people trust you, your recommendations can shape decisions. For example, what app might they use to solve a productivity challenge? This influence is a powerful tool, but it's grounded in the trust you’ve built over time.⁣ ⁣ READ MORE AT MY SUBSTACK ↓ ⁣ ⁣ https://lnkd.in/e2nnMZux

What are your thoughts on this product feature conversation? This is a conversation between A and B (they could be from product / business etc): --------- A: I really think we need feature X. B: Why do you think so? What does it solve for users? A: Because many people have the problem "Y" and I think "X" is the feature we need. Also, we should place the feature X on our app homepage. B: But I don't even think Y is a problem or that important a problem. Or X is worth building. Putting it on homepage is secondary decision. Multiple back and forths for next half an hour. And finally... A: Okay if you are not convinced, then let's AB test and see the data after launch. B. Ummm....i am not sure we should do that -----------

We’ve launched a powerful new update for JOSEPHA: 𝗦𝘁𝗮𝗿𝘁 𝘁𝗵𝗲 𝘀𝗲𝗮𝗿𝗰𝗵 𝗳𝗿𝗼𝗺 𝗮𝗻𝘆𝘄𝗵𝗲𝗿𝗲. Simply add "josepha.io/" in front of the URL of any product and access all relevant product information in one place. Why this feature? 🔍 𝗗𝗶𝗿𝗲𝗰𝘁 𝗦𝗲𝗮𝗿𝗰𝗵: We've heard our users! They wanted to start their product searches directly on any product page. Our users wanted a seamless experience - no app, no browser extension - and we're delivering just that. 💡 𝗤𝘂𝗶𝗰𝗸 𝗜𝗻𝘀𝗶𝗴𝗵𝘁𝘀: Our users were tired of spending hours browsing the web for test reviews to make informed purchasing decisions. We've got them covered! We provide a concise overview of the best reviews, helping our users save time and make informed decisions with ease. Plus, we cite the review pages, so they can verify key points themselves. Every day a step further on our mission to eliminate friction in shopping. See it in action (video below) and start searching with josepha.io/. 💬 What do you think of this new feature? Share your thoughts in the comments!

Look at this simple landing page and image how interactions can change the whole feel of the page?? I want to talk about interactions on a webpage or app this week and how it can improve the experience of user. Who is with me?? Who would prefer to see images of this instead of a video?? The image to this video is in the comment section below, for everyone asking. PS: what do you like about the simple page??

Deep-Dive into what's to come. Interact with your computer at the speed of light! Once again, your feedback is highly appreciated. This is a two-part video. 1. First Part: - I will touch base on the high level design of the app so you understand what you will get - I will showcase the expected values of the system 2. Second Part: - I demonstrate the app shortly so you can see what it does! P.S - Did you ever VoiceType before? If yes, how was your experience and how would you improve it?

An interesting insight today while taking a cab. I met a person who was taking his first ever ride and needed help with how to navigate the app. I asked him why he was not reading the instructions made for first timers by the app as I'm sure someone must have worked hard on it and done a lot of research. He mentioned that he just wanted someone to tell him which button to press to start a ride and which button to end it, everything else was pretty irrelevant. This just goes to show that an app may have a lot of different use-cases catering to different personas, but people are not bothered by this, they just want to know how their specific use-case can be solved in the least time possible. If they can get that information in their limited patience, they will stick otherwise they churn even if your app solved their use-case and they were just not able to find it. Hence, it is important to understand the core intent of the user and tailor make their FTUE (First Time User Experience) based on that. No matter how good your experience is, if it does not cater to people's specific use-cases, it won't matter :)

Lazy Loading: Load Only What You Need What is Lazy Loading? Lazy loading is a performance optimization technique that delays the loading of resources until they are actually needed. Instead of loading all the components, images, or data upfront, lazy loading ensures that only the necessary parts of your app are loaded when required. This approach can significantly reduce initial load times, making your app feel snappier and more responsive from the moment users start interacting with it.

Conversion of Numbers in Base Ten to Base Three Example Convert the following to base 3. 1) 4 2)8 3)16 Solution 1) 3| 4 3| 1 R 1 3| 0 R 1 3 = 11 ten three 2) 3| 8 3| 2 R 2 3| 0 R 2 8 = 22 ten three 3) 3| 16 3| 5 R 1 3| 1 R 2 3| 0 R 1 16 = 121 ten three Note: In this conversion, 3 is used to make the division because we are asked to convert in base 3. I hope you understand that there supposed to be a vertical line separating the value to be converted and the number that serve as a divisor in each case of division done. Since the app is not having a vertical line so we use this |. ASSIGNMENT Convert the following to numbers in base 3. 1) 9 ten 2) 23 ten 3) 142 ten

I've hit a common obstacle a lot of time - slow components due to re-calculating heavy tasks on each render. This hidden problem decreases our apps' speed and efficiency. So, what's the fix? I've found a strategy that really lights the way to smoother performance. Why bother with optimization? ✅User Experience: Fast apps feel great. They keep users happy and engaged. ✅Resource Management: Less unnecessary computation means more resources for other critical operations. ✅Battery Life: Optimized apps consume less power, extending battery life. `useMemo` By memorizing expensive operations, `useMemo` ensures they're only recomputed when absolutely necessary. ✅ Leverage useMemo for operations that don't need to run on every render. ❌ Allow expensive calculations to drain your app's vitality by running them more often than needed. From my experience, adding a bit of `useMemo` magic on performance-critical parts of your app can make a world of difference. It's a simple step that can lead to a dramatically better user experience. Drop your thoughts and questions below and let's make our React apps faster, together! 👇