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.
No web support is likely a bot mitigation strategy
How the new Threads app is made
241–250 of 251 posts
Re: How the new Threads app is made
#242Earlier quoted context omitted.
Both Jetpack Compose and SwiftUI came out around the same time, in 2019 I think. It's probably more correct to say that both frameworks copied React Native and made it more "native"
... and React Native copied the declarative approach of React, which copied WPF, which copied ... (no, we're definitely not the first ones to do declarative UIs here in 2023).
oh, its from wpf maybe thats why gearon interest in react that much because he have c# background
Re: How the new Threads app is made
#243Earlier quoted context omitted.
Would be surprised if this extension doesn't shrink in a subsequent release
Almost certainly just a dependency graph pruning issue. They likely pulled in too much of the main app into the plugin, which no longer has the strict sizing requirements that it used to. They'll trim it over the next couple of releases and the binary size shrink will look good on someone's performance review. Any kind of quantifiable changes like this counts as solid impact, heh, even if it has no real impact on usa…
Your comments vis a vis app size are not correct. App size (and battery consumption) have a strong, linear inverse correlation with initial downloads and engagement. There are a number of reasons users may not like large app sizes including being on a strictly data capped phone plan or having bad reception. Even reduction of megabytes showed big changes to engagement (often bigger than feature changes). Reducing app size was and I imagine continues to be a high level strategic priority at Facebook.
I agree with your overall conclusion however. Going to market with something is more important than optimizing for size.
Source: former FB employee
Re: How the new Threads app is made
#244Earlier quoted context omitted.
HN is downright quiet on the topic, with only 21 posts over 20 comments since the launch (2023-07-05), 4 posts per day. Compare that to the Reddit blackout posts which seem to be closer to 8 posts per day. Only 8 posts with over 100 comments, whereas it's hard to find even a single Reddit blackout post at less than 100 comments. My friends in every other community are buzzing about Threads, but here on HN someone com…
I think it's more that the HN crowd cannot stand to think, much less utter the phrase "you've gotta hand it to Mark Zuckerberg and crew." That's at least the feeling I have to get over when I praise Threads.
> I praise Threads.
Can't praise a thing I can't access,
Yours truly,
- EU citizen
P.S no web interface in 2023?
Re: How the new Threads app is made
#245The hype doesn’t feel organic, and neither do the posts from brands on Threads.
Some examples, which feel like they were written by the same social media intern:
https://twitter.com/chrisbeach/status/1677584064436477952
As for the app itself, feels very bare bones to me, and I dislike Zuckerberg locking us into another walled garden with no web access.
Re: How the new Threads app is made
#24672 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.
Twitter Lite, which covers more use cases than Threads is 0.5 MB.
Re: How the new Threads app is made
#247I'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 rea…
yea it was pretty obvious they were spamming on the day, when you could see numerous reddit posts announcing that "threads is launching" with pretty much the exact same title in multiple subreddit, all from different accounts.
Re: How the new Threads app is made
#248>This suggests that their sign-in experience isn’t native and they are showing a webview. what is the benefit of using webview instead native for the sign-in?
OAuth flows typically end up needing to load a web view in many cases (like, signing up through Facebook) but also simpler implementation / code reuse
Re: How the new Threads app is made
#249Have 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...
Wow, is that the actual app? It took so long, like five or six seconds, to load a few short sentences.
Re: How the new Threads app is made
#250Earlier quoted context omitted.
Both Jetpack Compose and SwiftUI came out around the same time, in 2019 I think. It's probably more correct to say that both frameworks copied React Native and made it more "native"
... and React Native copied the declarative approach of React, which copied WPF, which copied ... (no, we're definitely not the first ones to do declarative UIs here in 2023).
React definitely did not copy WPF. It copied XHP: https://docs.hhvm.com/hack/XHP/introduction which was another Facebook thing, but that itself was inspired by E4X: https://en.m.wikipedia.org/wiki/ECMAScript_for_XML