Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How the new Threads app is made

emergetools.com

Post reply on HN
Print view View original

91–100 of 251 posts

Re: How the new Threads app is made

#91

Post by epistasis »

wouldbecouldbe wrote: post #71
epistasis wrote: post #50

Earlier quoted context omitted.

Features are a looooooong second place to userbase. Hashtags mean nothing compared to having millions of users to interact with. Launching in a hurry to capitalize on the mistakes of your competitors is an amazing plan. Better to ship without the feature than to ship the wrong feature and be stuck with the tech debt. Better to launch and acquire users when possible, and slowly add the necessary parts. A far more impo…

Hahah I love the bias here. Musk ships & changes things on the fly, Twitter is going to hell. Zuck releases threads, amazing he dears to launch an MVP that fast.

Isn't it far more biased to assume that anything Musk ships is good?

Features and shipping should be evaluated empirically by results, not by deciding a priori that the decision maker is good or bad.

So I think you might be projecting a bit with your bias. And for that matter, I didn't even mention Musk's changes at all, yet you seem to be grouping me in with people that have! (But for the record, I preferred the feature set of Twitter before Musk started changing things. Still, the feature changes are still a loooot less important than the user base. And by prioritizing replies by paying versus non-paying customers, the user base that I experience on Twitter has gone down in quality by a ton, meaning that it is far less useful. That and shutting down the site for a few days and letting me experience zero of the user base-or rather a feed refresh two reply threads before 600 tweets were hit-was completely boneheaded. Stupid. B-player move.

Re: How the new Threads app is made

#94

Post by lern_too_spel »

MisterSandman wrote: post #48
troupo wrote: post #38

Earlier quoted context omitted.

People care. You just refuse to listen to what they say. They say things like "my internet cap is reached", "my battery is drained faster", "my phone is slow" and a million other things that oblivious and clueless programmers don't hear because they can only hear when someone talks about megabytes, cpu cycles, RAM etc.

> my internet cap is reached 1. The vast majority of the world now has access to very high or unlimited data packs. This is hardly the big issue that HackerNews makes it out to be. 2. Threads' main user base is Instagram. An hour of watching Instagram Reels is more data than the entire Threads app. I highly doubt Instagram users are data strapped. > "my battery is drained faster" App size has nothing to do with how m…

> 2. Threads' main user base is Instagram.

Those users already have Instagram. Threads is competing against Twitter clones.

> App size has nothing to do with how much battery is drained out.

Larger apps use more radio, use more CPU for decompression, use more flash writes on updates. All use battery. Decompression and writes for background updates slow the phone. The additional flash writes lead to wear causing storage to become slower even when the app is not being used or updated.

Re: How the new Threads app is made

#95

Post by lern_too_spel »

colesantiago wrote: post #36
lern_too_spel wrote: post #30

72 MB is egregious for a Twitter-clone MVP. For comparison, the full-featured Twitter app itself is 40 MB. The Mastodon app weighs in at 1.6 MB.

This didn't stop 70M+ users from downloading the app and using it. Nobody cares.

Some fraction of the 1 billion+ who didn't download the app care, including me.

Re: How the new Threads app is made

#96

Post by ryandrake »

I'm kind of amazed at how saturated the news is with stories about Threads. And not just tech news, but also every mainstream news site has at least one or more "submarine" marketing articles promoting Threads. Meta Marketing Team: You're not fooling anyone into thinking these are grassroots and viral, but honestly, well done with the media saturation. Meta's clearly got all the right channels on full-blast. It's really impressive.

Re: How the new Threads app is made

#97

Post by codetrotter »

pootusmaximus wrote: post #92
wbobeirne wrote: post #4

Have there been any public plans for a fully featured web app? Having it be read-only on the web is a non-starter for me.

Yes > the priority is the mobile apps, but we are working on www https://www.threads.net/t/CuWp3eMNE8h/?igshid=NTc4MTIwNjQ2YQ...

Is threads.net the official website?

This is the first time I actually look at anything that is on the Instagram Threads.

Seems a lot like the comments under an Instagram post, without the picture / video on top.

Also the logo on the top of the page just toggles dark mode / light mode, instead of bringing me to any kind of home page where I can explore more discussions.

Weird.

Re: How the new Threads app is made

#99

Post by [deleted] »

Infinitesimus wrote: post #86
wouldbecouldbe wrote: post #72

Honestly threads is so minimum. A solo dev can pull this off in half a year. Only thing complicated is scale. But meta has that in place. Threads team is a corporate cushion team.

> A solo dev can pull this off in half a year. > Only thing complicated is scale So, a solo dev cannot, in fact, pull this off.

[deleted]

Re: How the new Threads app is made

#100

Post by mustacheemperor »

wouldbecouldbe wrote: post #71
epistasis wrote: post #50

Earlier quoted context omitted.

Features are a looooooong second place to userbase. Hashtags mean nothing compared to having millions of users to interact with. Launching in a hurry to capitalize on the mistakes of your competitors is an amazing plan. Better to ship without the feature than to ship the wrong feature and be stuck with the tech debt. Better to launch and acquire users when possible, and slowly add the necessary parts. A far more impo…

Hahah I love the bias here. Musk ships & changes things on the fly, Twitter is going to hell. Zuck releases threads, amazing he dears to launch an MVP that fast.

>Musk ships & changes things on the fly

I don't think it's biased to be a lot less impressed by "things" like dragging your engineers in over the weekend over the threat of termination if they can't make your own tweets more popular.

>His deputies told the rest of the engineering team this weekend that if the engagement issue wasn’t “fixed,” they would all lose their jobs as well.

>Late Sunday night, Musk addressed his team in-person. Roughly 80 people were pulled in to work on the project, which had quickly become priority number one at the company. Employees worked through the night investigating various hypotheses about why Musk’s tweets weren’t reaching as many people as he thought they should and testing out possible solutions.

That's not impressive, it's reprehensibly poor management of people both as human beings and as company resources. There's no way I can figure how to view this story as a laudable effort to ship fast and iterate the platform quickly.

[0]https://www.theverge.com/2023/2/14/23600358/elon-musk-tweets...

Post reply on HN