IMHO, the reasons mentioned are not very convincing. Your goal, when starting a product, is to find whether you serve a real user need or not. So, start with a website or a mobile app depending on what suits your users needs better. Where would a user naturally go (web or mobile) for that need? That's the platform you start with.
Very frequently, the right answer for an MVP is something like "an e-mail newsletter" or "a Salesforce extension" or "a CSV file" or "an IDE plug-in" or "throwing a pizza party for your target market and performing the service for them yourself". I've seen startups charge $3K+/month to dump a CSV file on a client's FTP server. Go where the user can most conveniently make use of your product; for a lot of businesses,…
Start with a Website, Not a Mobile App
211–220 of 587 posts
Re: Start with a Website, Not a Mobile App
#212Earlier quoted context omitted.
For those who can't stand javascript, typescript was made for you
Typescript is just a huge bandage. It doesn't change that JavaScript has horrible tooling that changes every full moon. Not to mention it still keeps many of JavaScript's horrible warts.
Which "warts" does Typescript keep from Javascript?
Re: Start with a Website, Not a Mobile App
#213I am moving towards "Windows app first"; Windows still has dominant market share among Desktop users. You might impress investors and developers with Mac and Linux support, but far too many people are developing for platforms where the users are not and wondering why their stuff isn't catching on.
Meh... I'd lean towards web app first, wrapping in cordova for ios/android and electron for desktop at first... adding in more native features as time moves forward, probably react native for {platform} as a second stage.
Re: Start with a Website, Not a Mobile App
#214Earlier quoted context omitted.
> I don't have time to research whether or not they are going to abuse my privacy or have some horrendous TOS. Do you think that web apps are better in that regard?
Yes. I don't give them permission to run code on my device arbitrarily and perpetually. Think of it like this: If Hacker News required a fat client to function on your desktop, would you actually be here at all?
Re: Start with a Website, Not a Mobile App
#215I don't even bother installing apps anymore, I don't have time to research whether or not they are going to abuse my privacy or have some horrendous TOS. I got my core 10 apps and haven't bought a new one in a year.
I figure most things don't need an app unless they are trying to take more data anyway. Anything telling me to install an app whose mobile experience is fine already is very fishy to me. I'm looking at you, Reddit.
I prefer "Reddit is Fun" which seems to load faster than mobile web reddit and notify me on comment replies.
Re: Start with a Website, Not a Mobile App
#21680% of apps are uninstalled in the first 10min (especially if they ask for information or creating an account). Once uninstalled very unlikely they will ever install again. In my dev shop, I always advise clients to look into website MVP over apps unless IT IS CRITICAL to the functionality. Websites can always bring back ppl who were initially uninterested. Faster development/instant updates. Better tracking and UX a…
How many websites ever get passed the signup stage? I often will leave as soon as I'm tasked with creating an account and I'm not likely to come back.
Now the solution is of course to have a separate gmail account to register. Most sites still allow user+site@gmail.com address syntax so that I can sometimes see who are leaking where.
I would be curious to know if there is some credible A/B testing showing that for a relatively unknown new product blocking Mailinators and it’s kin somehow results as a better conversion?
Re: Start with a Website, Not a Mobile App
#217Earlier quoted context omitted.
I saw it for the first time last night. I think it was Vimeo. It was actually much better than the "try our app" popup, because it was android asking if i wanted to use the instant app, and when i said no it just went away.
That's more reasonable. I wonder if these work via Firefox? Maybe that's why I've never seen them.
Re: Start with a Website, Not a Mobile App
#218Earlier quoted context omitted.
I like this concept. Using the smart phone more like a PDA than a tiny laptop. What are your 10 core apps if you don't mind sharing?
For me: Personal Capital (finance), WhatsApp, Slack, Overcast (podcasts), Kindle, Dark Sky (hyper accurate weather app), Google Authenticator, Lyft, RENPHO (my smart scale’s app), 1Password Everything else is very situational and totally optional.
Re: Start with a Website, Not a Mobile App
#219Earlier quoted context omitted.
Yes. I don't give them permission to run code on my device arbitrarily and perpetually. Think of it like this: If Hacker News required a fat client to function on your desktop, would you actually be here at all?
While I agree on your point, your comment made me smile as I’m reading HN using a mobile app
Re: Start with a Website, Not a Mobile App
#220Earlier quoted context omitted.
iOS doesn’t support push notifications for web pages.
Are Safari push notifications desktop only? https://developer.apple.com/notifications/safari-push-notifi...
https://www.izooto.com/blog/ios-push-notifications-safari
And this might be why....
Web Push Notifications have clearly made difference in every marketing campaign it gets involved in.