Start with a Website, Not a Mobile App
491–500 of 587 posts
Re: Start with a Website, Not a Mobile App
#492Earlier quoted context omitted.
I would take that even further and venture a guess that 99% of HN readers are not representative of the intended general userbase of 99% of the apps for ios/android.
As a side note, 99% of the statistics are made up, including this very sentence.
Re: Start with a Website, Not a Mobile App
#493Earlier quoted context omitted.
I would take that even further and venture a guess that 99% of HN readers are not representative of the intended general userbase of 99% of the apps for ios/android.
Also called the Malkovich Bias.
Re: Start with a Website, Not a Mobile App
#494Earlier quoted context omitted.
This is my position as well. Unless your app is going to provide substantial features over your website or operating system like functionality. I'm not even going to try it out.
I don't go to new websites anymore either. Just like I have a handful of core apps, I have about he same number of websites I visit. I think the only webapps I use are Workflowy (love it) and Slack (hate it).
I'm a pretty heavy user of it, and it was a godsend to have a nice official Android client that works well. Make use of the web lots on the desktop but it's probably 50/50 desktop/mobile. Love them both .
The only two things workflowy is missing is (1) being able to embed pictures and (2) being able to hyperlink to other nodes to make it act like a graph. It'd be the absolute perfect tool if it had that.
Re: Start with a Website, Not a Mobile App
#495I'd like to venture another guess even further that this is possibly the furthest venture anyone can guess.
Re: Start with a Website, Not a Mobile App
#496>An App Store developer license costs $99/year, whereas a Namecheap domain is less than $10/month. "A developer license is $99/year, but a website is less than $120/year!" Very weird statement.
Re: Start with a Website, Not a Mobile App
#497Reminds me of the time when WIRED magazine back in 2010 declared the web 'dead.' [0] Kind of amusing to note how wrong they were. [0] https://www.wired.com/2010/08/ff-webrip/
Re: Start with a Website, Not a Mobile App
#498Earlier quoted context omitted.
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.
>Anything telling me to install an app whose mobile experience is fine already is very fishy to me. Facebook is my #1 example of this. The app bloated up like it's primary purpose was to take up space on your phone. So I removed it and used the mobile website. At first you had to refresh the page to get new messages. No big deal, but a bit annoying. Then they updated and didn't even need to refresh the page to get an…
Re: Start with a Website, Not a Mobile App
#499Earlier quoted context omitted.
What is especially frustrating that many sites don’t allow Mailinator and other similar ‘one-time’ email systems to be used for registering an account. No way I am going to give you my email address up front before seeing the product. 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.…
There is a lot of temporary email services constantly popping into the Internet every month. Some of them are open-sourced so one can make own quick disposable email or forwarding service with cheap domain. "Resistance Is Futile" - no way any exclusion list can keep up to cover them.
Re: Start with a Website, Not a Mobile App
#500I'd like to venture another guess even further that this is possibly the furthest venture anyone can guess.