News for hackers. Stuff that matters.
Re:Start with a Website, Not a Mobile App by geezerjay on Friday January 04, 2019 @03:36PM (#18827366)
> Think of it like this: If Hacker News required a fat client to function on your desktop, would you actually be here at all?

HN essentially is a service that provides only a couple of text views to list and read submittions and their discussions, and requires zero processing or interaction. That's hardly a challenging problem that requires a fat client.

If however we were discussing an application that required significant data processing, access to your personal data, or even access to photo ir video input... You'd hardly be able to implement something with HTML+CSS.

Case in point: twitter is very usable as a website but instagram is not.

Re:Start with a Website, Not a Mobile App by notSupplied on Friday January 04, 2019 @06:06PM (#18828598)
On mobile, you don't use a fat client for HN? I've even paid money for an app (MiniHack) to have a nicer experience on mobile.
Re:Start with a Website, Not a Mobile App by geezerjay on Friday January 04, 2019 @06:11PM (#18828636)
Truth be told, a full blown mobile app isn't needed to tweak the UI or provide different views.
Re:Start with a Website, Not a Mobile App by code_duck on Friday January 04, 2019 @03:45PM (#18827433)
They wouldn’t have to change much about Instagram to make it into Twitter.
Re:Start with a Website, Not a Mobile App by geezerjay on Friday January 04, 2019 @04:04PM (#18827597)
If you take away those features then you cease to have instagram.

Instagram users only use instagram because it provides access to those functionalities.

Re:Start with a Website, Not a Mobile App by code_duck on Saturday January 05, 2019 @09:27AM (#18831753)
What functionality are you referring to? The only one I can think of is photo editing. It’s not that difficult to make a photo editor in the browser. The only problem is performance. It would’ve been harder when Instagram was originally launched.
Re:Start with a Website, Not a Mobile App by bgarbiak on Friday January 04, 2019 @04:18PM (#18827725)
Instagram is perfectly usable as a website, at least on an iPhone. I guess some features might be missing, but the core stuff is there: browsing, adding photo, filters, stories.
Re:Start with a Website, Not a Mobile App by sosborn on Friday January 04, 2019 @04:33PM (#18827845)
How do you post a photo on instagram in a web browser? I thought that was reserved for the app.
Re:Start with a Website, Not a Mobile App by payamb on Friday January 04, 2019 @07:07PM (#18828961)
You can post a photo on instagram in a browser on iphone. you also can on other platforms by changing your useragent to webkit
Re:Start with a Website, Not a Mobile App by syrrim on Friday January 04, 2019 @04:56PM (#18828049)
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.
Re:Start with a Website, Not a Mobile App by sosborn on Friday January 04, 2019 @05:07PM (#18828142)
Interesting, they don’t seem to allow this on the desktop browser. Changing the user-agent yo a mobile browser exposes it. What a strange decision.
Re:Start with a Website, Not a Mobile App by laurentl on Friday January 04, 2019 @06:08PM (#18828615)
I don’t use Instagram so can’t check the code, but I would guess they use something like

    <input type="file" accept="image/*" capture>
Which does what you’d expect on a mobile device (launch the camera) but behaves differently on desktops (opens a file upload dialog). They may have decided that this behavior would confuse users.
Re:Start with a Website, Not a Mobile App by geezerjay on Friday January 04, 2019 @06:09PM (#18828617)
How do you ensure that a client only sees a picture/video once and can't save it?
Re:Start with a Website, Not a Mobile App by code_duck on Friday January 04, 2019 @08:20PM (#18829261)
The photos are available as publicly accessible jpgs through http. They’re not really trying to do that.
Re:Start with a Website, Not a Mobile App by cschep on Friday January 04, 2019 @07:25PM (#18829028)
You can't ensure this natively either.
Re:Start with a Website, Not a Mobile App by da_chicken on Friday January 04, 2019 @05:26PM (#18828303)
> 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 to go to the market to get a carton of milk." Suddenly your listener stops you and says, "But I don't like milk."

If your response to the above paragraph is, "But I don't know how network services work," then, congratulations, you can look forward to an exciting career in either comedy or politics, depending on whether or not you were serious.

Re:Start with a Website, Not a Mobile App by dang on Friday January 04, 2019 @09:45PM (#18829572)
Can you please not post flamewar-style comments to HN, regardless of how wrong or provocative you find another comment? We're trying for better than this here.

https://news.ycombinator.com/newsguidelines.html

[dead]
Re:Start with a Website, Not a Mobile App by zrobotics on Friday January 04, 2019 @08:10PM (#18829215)
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 by rjsw on Friday January 04, 2019 @07:53PM (#18829139)
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.