Live data from Hacker News

Start with a Website, Not a Mobile App

atrium.co

411–420 of 587 posts

Re: Start with a Website, Not a Mobile App

#411
post #323

Earlier quoted context omitted.

Add a file input -> the users taps it -> ios asks if they want to use an existing photo or take a new one -> take a new photo. Result on android may differ.

How do you ensure that a client only sees a picture/video once and can't save it?

You can't ensure this natively either.

Re: Start with a Website, Not a Mobile App

#412

80% 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…

Where did you get that 80% from? I have hard time believing the average Joe uninstalls an app

Re: Start with a Website, Not a Mobile App

#413

Earlier quoted context omitted.

We've been hearing the same pitch for literally years. Heck, I've made some of them myself: "This is it, people! Native apps have been rendered unnecessary!" No PWA competes with a native experience. Not performance wise, not usability wise, and ultimately for the developer not even development wise. It may still make a lot of sense, and there are a lot of arguments for web apps, but the enthusiasm in this discussion…

That's because Apple and Google are doing everything in their power to keep apps tied to their app stores. If they wanted to they could make progressive apps runs as smooth as native apps tomorrow by enabling better native integration, but they won't.

Google makes a ton more money off of web search than their app store and they keep releasing new features that allow you to access your devices sensors so I doubt that for google.

Re: Start with a Website, Not a Mobile App

#414

Earlier quoted context omitted.

well i had a different experience. we dong have a native app, but some of our b2b customers wanted an "app" to use on mobile. The app is responsive so we show them how to add it to homescreen and that's it.

It might be business customers are more willing to jump through hoops. My website is targeted at the general public in a small midwestern town, where technology is a four letter word.

Indeed. Business customers aren't representative of the greater public because they tend to take their issues directly to IT support, they get it sorted, and don't think about it again. Your every day average user doesn't have an IT support department to which to go. They do, however, have the App Store/Play Store.

Re: Start with a Website, Not a Mobile App

#417

Earlier quoted context omitted.

> That's hardly a challenging problem that requires a fat client. That's irrelevant. It doesn't matter that making a fat client for HN isn't necessary; that's completely beside the point. You're looking for reasons to ignore the stated premise of an analogy rather than accepting that the premise would be true. It's like this. Say you were beginning to explain how network services work with an anecdote: "Say you need…

> That's irrelevant. It doesn't matter that making a fat client for HN isn't necessary; that's completely beside the point. If that's your take then you've completely missed the whole point. The functionalities made available to mobile applications are the reason why they exist. Developers don't work on mobile applications for the sake of working on mobile applications. They are paid to develop clients that take adva…

I would suggest that quite a few people write mobile applications because their managers tell them to do it. This is totally independent of whether the use case requires a mobile application.

Re: Start with a Website, Not a Mobile App

#418
Antidotal (likely an outlier) but I’ve slowly deleted social apps (Facebook, Twitter, insta) in favor of using their mobile sites. My reasoning is three fold: mobile sites are pretty good, it’s harder for companies to mine my data in a browser, and honestly storage on my 16gig iPhone is far too valuable for a 300mb app!! I’m 18 (aka young and woke) btw.

Side point: I still need Snap’s app but I’ve considered quitting altogether bc it’s barely usable on my 6S. If battery is < 10% my phone will die if I open SC

Re: Start with a Website, Not a Mobile App

#419

Earlier quoted context omitted.

> That's hardly a challenging problem that requires a fat client. That's irrelevant. It doesn't matter that making a fat client for HN isn't necessary; that's completely beside the point. You're looking for reasons to ignore the stated premise of an analogy rather than accepting that the premise would be true. It's like this. Say you were beginning to explain how network services work with an anecdote: "Say you need…

> That's irrelevant. It doesn't matter that making a fat client for HN isn't necessary; that's completely beside the point. If that's your take then you've completely missed the whole point. The functionalities made available to mobile applications are the reason why they exist. Developers don't work on mobile applications for the sake of working on mobile applications. They are paid to develop clients that take adva…

Ok, jumping in here. So yes, HN doesn't 'need' a full app, but the functionality difference between this site and Reddit isn't that great. So why, pray tell, does Reddit nag me every time I visit on mobile?

It certainly isn't that the app provides functionality that isn't avaliable through the browser, but somebody decided that it was worth spending development time and nagging users over. So yes, there are things that can't be implemented through the browser and require an app, but it's incorrect to state that nobody develops an app unless they absolutely need to.

Re: Start with a Website, Not a Mobile App

#420
post #369

Earlier quoted context omitted.

On one hand I can see rational reasons for them not allowing it; Apple doesn't control when you push updates to your PWA, so they don't want to give their seal of approval by listing it in the app store. But on the other hand, it's pretty depressing to give up the dream of instant app updates, by wrapping your shiny PWA in Cordova and promising to never execute external JavaScript.

Pushing updates without going through the app store has been allowed by Apple as long as the assets being updated are not binary code; specifically CSS, HTML, and JavaScript are okay (I wonder whether WebAssembly will be considered "binary" or not... will be interesting to see). I convinced a former employer to abandon their Xamarin-built app and switch to Ionic (Cordova with nice, fancy UI additions) specifically be…

Ionic CEO here - have seen no issues with anyone using our deploy (web-content remote update) feature on either platform to date
Post reply on HN