Farid Sultani

Farid Sultani

Building useful things for society.
5 points

About

I'm a self-taught developer who loves building awesome and useful things.

Badges

Tastemaker
Tastemaker
Gone streaking
Gone streaking
Gone streaking 5
Gone streaking 5

Maker History

  • Aalim.chat
    Aalim.chat
    Your friendly Muslim scholar
    Feb 2024
  • 🎉
    Joined Product HuntFebruary 9th, 2024

Forums

Farid Sultani

1yr ago

Mobile web vs native

I just launched yesterday, and the feedback and support has been incredible. I wanted to share a product decision I made, and get your thoughts. I built my app for the web, then optimized it for mobile devices since I have users on both platforms. I know it's probably more common to build mobile apps natively, but I feel like there might be a downside to this approach, which is that it can create friction for users who just want to test your app. Making them go to an app store (whether it's from Apple or Google) and download isn't hard, but it is an extra step they have to take just to try your app. If it's on mobile web, they can immediately begin using it since all phones have built-in web browsers. I actually got this idea from Perplexity, which was what inspired me. I feel like removing that "barrier" (for lack of a better word) of requiring a user to download the app just to test it out can reduce friction, ultimately leading to more users. I know this can't work for all products since plenty of apps need a device's native functionality, but for those that can function as web apps, I think it can be a good option. Once you get enough users using the app, you can offer them the native version. In full transparency, I build for web, not mobile. Still, that wouldn't stop me from building a native app.

View more