4 ms·

> Threads has one of the largest plugins we’ve ever seen. BarcelonaShareExtension is 81 MB. For context, the largest Instagram plugin - InstagramNotificationExt

> Threads has one of the largest plugins we’ve ever seen. BarcelonaShareExtension is 81 MB. For context, the largest Instagram plugin - InstagramNotificationExtension is 23.5 MB. TheInstagramShareExtension is 5.6 MB Out of a 244.2 MB App on iOS.

tough 3y ago
Why the heck would they need an extension to share "Barcelona" Are we talking the whole city map or like wut
- cpeterso 3y ago
  "Barcelona" is the code name of the Threads project. The Threads Android app is called "com.instagram.barcelona".
  - PaulHoule 3y ago
    Maybe they should have named it something other than "Threads", the other day it just got out that these guys https://threads.com/ https://threads.com/ have a trademark filing for "Threads" as a name for a communications service. If I picked out the right two screenshots you might have a hard time telling them apart https://tsdr.uspto.gov/#caseNumber=87522273&caseType=SERIAL_NO&searchType=statusSearch https://tsdr.uspto.gov/#caseNumber=87522273&caseType=SERIAL_... and "Threads Group, Inc." is really the people behinds threads.com https://www.crunchbase.com/organization/threads-aa50 https://www.crunchbase.com/organization/threads-aa50 "Barcelona" might really have been available. "Threads Group, Inc." would be within their rights to make Meta change the name.
    - explain 3y ago
      > "Threads Group, Inc." would be within their rights to make Meta change the name. Meta's use of the term "Threads" for a communications service likely actually predates or at least rival's "Threads Group, Inc.". Meta had an app called Threads until it was shut down in late 2021.
- deleted 3y ago
  [deleted]
ra 3y ago
“Just ship it already” … dependency bloat is not a valid complaint for a new product.
- grishka 3y ago
  Stack choice is extremely important. Your best possible performance/binary size/resource usage is a function of your stack. You make that choice in minutes when starting a new project, but then it haunts you for years. If you built your desktop app with Electron for example, you can't just ditch it at once down the road — switching to something better would be a serious, laborious, long undertaking. It might be easier to just chuck the thing altogether and start from scratch.
maxptop 3y ago
Would be surprised if this extension doesn't shrink in a subsequent release
- arcticbull 3y ago
  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 usage. Let's be honest, nobody cares how big it is, so long as it doesn't force you to download over WiFi. Nobody sorts the App Store by 'size.' It's more important in the initial release to prove product market fit rather than spending time whittling down the share extension. They made the right call to get to market fast.
  - tschwimmer 3y ago
    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
  - coldcode 3y ago
    They are missing substantial features like hashtags and follows, leaving you at their mercy to show you content. That would imply it's just a WIP shipped to nearly 100M people. It's doubtful it will ever shrink, given how much is missing, unless it's in there but not production quality. My guess is they shipped it in a hurry, and now there is enormous pressure on them to add all the missing features quickly, never a good plan.
buildbot 3y ago
What could it possibly need that much code for
- deleted 3y ago
  [deleted]
- kyleyeats 3y ago
  All the other stuff it did when it was the prior project called Threads from a couple years ago.

tough 3y ago

Why the heck would they need an extension to share "Barcelona" Are we talking the whole city map or like wut

cpeterso 3y ago
"Barcelona" is the code name of the Threads project. The Threads Android app is called "com.instagram.barcelona".
- PaulHoule 3y ago
  Maybe they should have named it something other than "Threads", the other day it just got out that these guys https://threads.com/ https://threads.com/ have a trademark filing for "Threads" as a name for a communications service. If I picked out the right two screenshots you might have a hard time telling them apart https://tsdr.uspto.gov/#caseNumber=87522273&caseType=SERIAL_NO&searchType=statusSearch https://tsdr.uspto.gov/#caseNumber=87522273&caseType=SERIAL_... and "Threads Group, Inc." is really the people behinds threads.com https://www.crunchbase.com/organization/threads-aa50 https://www.crunchbase.com/organization/threads-aa50 "Barcelona" might really have been available. "Threads Group, Inc." would be within their rights to make Meta change the name.
  - explain 3y ago
    > "Threads Group, Inc." would be within their rights to make Meta change the name. Meta's use of the term "Threads" for a communications service likely actually predates or at least rival's "Threads Group, Inc.". Meta had an app called Threads until it was shut down in late 2021.
deleted 3y ago
[deleted]

ra 3y ago

“Just ship it already” … dependency bloat is not a valid complaint for a new product.

grishka 3y ago
Stack choice is extremely important. Your best possible performance/binary size/resource usage is a function of your stack. You make that choice in minutes when starting a new project, but then it haunts you for years. If you built your desktop app with Electron for example, you can't just ditch it at once down the road — switching to something better would be a serious, laborious, long undertaking. It might be easier to just chuck the thing altogether and start from scratch.

maxptop 3y ago

Would be surprised if this extension doesn't shrink in a subsequent release

arcticbull 3y ago
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 usage. Let's be honest, nobody cares how big it is, so long as it doesn't force you to download over WiFi. Nobody sorts the App Store by 'size.' It's more important in the initial release to prove product market fit rather than spending time whittling down the share extension. They made the right call to get to market fast.
- tschwimmer 3y ago
  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
- coldcode 3y ago
  They are missing substantial features like hashtags and follows, leaving you at their mercy to show you content. That would imply it's just a WIP shipped to nearly 100M people. It's doubtful it will ever shrink, given how much is missing, unless it's in there but not production quality. My guess is they shipped it in a hurry, and now there is enormous pressure on them to add all the missing features quickly, never a good plan.

buildbot 3y ago

What could it possibly need that much code for

deleted 3y ago
[deleted]
kyleyeats 3y ago
All the other stuff it did when it was the prior project called Threads from a couple years ago.