Threads on Android Leaves Australian Users Wanting More

When Meta launched Threads in July 2023, the platform was pitched as the Twitter alternative the world had been waiting for. Early momentum was extraordinary, with over 100 million users signing up within days, mostly through Instagram. The Android client, however, has never quite matched that initial energy. Months on, Australian users juggling Telstra and Optus connections are discovering that the app behind the buzz feels undercooked, with sluggish performance, unreliable notifications, and a feature set that lags behind both X and Bluesky.

The gap between the marketing and the mobile reality matters because Threads sits at the centre of Meta's broader social strategy, especially as the company prepares for further integration with the fediverse. For anyone relying on Android as their daily driver, the experience is a curious mix of polished UI fragments and unfinished plumbing. A closer look at performance, notifications, and what is still missing reveals why so many users have quietly drifted back to the apps they were trying to leave.

Performance stumbles on everyday Android hardware

Benchmarks only tell part of the story, because most Australians are not running flagship Samsung Galaxy S24 Ultras or Pixel 8 Pros. The bulk of the local market sits with mid-range devices, including Samsung Galaxy A series handsets, Motorola Edge models, and Nokia-branded mid-tiers sold through JB Hi-Fi and Officeworks. On these phones, Threads exhibits noticeable stutter when scrolling through the main feed, particularly with images and short-form reels mixed into text-heavy threads.

The app's RAM usage spikes aggressively when switching between the activity feed and direct messages. Cold start times on a Telstra 5G connection in suburban Melbourne routinely sit between four and six seconds, which is sluggish compared to X or even Instagram itself on the same hardware. Animations occasionally drop frames, and pinch-to-zoom produces a brief but jarring freeze. Collectively, the experience feels heavier than it should for an app of its scope.

There are also signs that Threads still carries unfinished code paths. Crash reports have appeared in the Google Play Console for devices running Android 13 and earlier, especially when the app is left running in the background. The image-heavy version can struggle with cold cache loads while older builds remain finicky on entry-level chipsets, frustrating users who expected a smooth, native Android feel from one of the world's largest tech companies.

Notifications remain the app's weakest link

If there is one complaint that unites Australian Threads users, it is the unreliable notification behaviour. The app routinely delays activity alerts by several minutes, even on devices set to unrestricted battery optimisation. Push delivery is particularly inconsistent on Vodafone's 3G fallback towers in regional Queensland and Western Australia, where users see batches of notifications arriving only when they manually open the app.

Beyond timing, the categorisation feels half-baked. Threads bundles replies, mentions, and quote-posts into a single notification stream with no granular controls to separate them. Users cannot mute specific thread participants without leaving the thread entirely, and there is no equivalent of X's quality filter. The lack of granular control is stark when you consider how other modern apps handle similar complexity. Even connected home platforms governed by the Matter 1.3 specifications offer more thoughtful alert hierarchies than Threads currently manages.

Battery drain is another quiet concern. The Threads service uses background tracking that occasionally fattens power use, particularly when location-based features are enabled. Australian reviewers at local tech outlets have flagged idle drain of 8-12 per cent overnight on Pixel devices, well above what a backgrounded social app should consume. For users already running Battery Saver mode to stretch through a long shift, that number becomes a deal-breaker.

Where the notification system falls short

• Push delivery on regional carriers delays alerts by several minutes
• Reply, mention, and quote-post alerts share a single non-filterable stream
• Idle battery drain reaches 8-12 per cent overnight on Pixel hardware
• No mute option for individual participants within active threads

Features that should have shipped on day one

Even accounting for Threads' youth, the feature gap compared to competing platforms is striking. There is no edit button, no proper chronological feed toggle that persists across sessions, and no support for scheduled posts. The desktop experience is a web wrapper that lacks keyboard shortcuts and fails to load on some Australian corporate networks. Documentation across our coverage archives shows how persistent these gaps have been since launch.

The list of omissions keeps growing when you compare it with Bluesky's custom feeds or Mastodon's community-driven moderation tools. For a platform owned by Meta, the absence of basic utilities feels deliberate, as if Threads is being kept lean to avoid cannibalising Instagram's Reels effort. Small business operators who sell through Instagram and need a text-first companion have been vocal about the missing tools.

A small but telling detail: Threads still cannot properly handle link previews from many Australian news domains. Drop a Sydney Morning Herald or ABC Australia URL into a post and the unfurled card frequently returns a broken thumbnail or truncated description. That is awkward for journalists and creators who depend on clean sharing.

Features still absent from the Android client

• No edit button for published posts after the original send
• No persistent chronological feed toggle across app sessions
• No scheduled post or queued draft support on mobile
• No proper link unfurling for major Australian news domains

How the network behaves on Australian carriers

Carrier-level behaviour shapes app experience far more than most US-centric reviews admit. On Telstra's mid-band 5G in Sydney's CBD, Threads loads text reliably but stumbles on video-heavy threads, frequently downgrading resolution. Optus users in Adelaide and Perth have reported the opposite pattern, with video playback performing well but text threads occasionally failing to refresh after a swipe-down gesture.

Vodafone Australia subscribers, a smaller cohort, see the most erratic results, with the app frequently timing out on long image carousels. These are not catastrophic outages, but they create uneven experiences that depend entirely on which carrier logo appears in your status bar. The Threads service uses aggressive image prefetching that occasionally overruns data caps, particularly on prepaid plans. The image-heavy variant can chew through 200-300MB in a single hour of casual scrolling, which adds up quickly on plans that price data at a premium.

DNS lookups and CDN routing appear to favour Meta's overseas infrastructure, with connections frequently terminating in Singapore or US-west data centres rather than closer Sydney nodes. This contributes to the slight but persistent lag that Australian users notice compared with Instagram proper. For a country that built its broadband ambitions around the NBN, the routing feels oddly dated.

Where Threads sits inside Meta's wider ecosystem

The whole point of Threads, according to Meta's leadership, is that it eventually becomes a fully federated platform speaking the same protocols as Mastodon and the wider ActivityPub network. On Android, however, the fediverse functionality still feels half-implemented. Users can see Mastodon replies threaded beneath their posts in some regions, but the toggle is buried several menus deep and frequently disappears after a fresh install.

The integration with Instagram feels more polished but equally restrictive. Switching between the two apps is seamless for scrolling, but transferring anything meaningful between them is harder than it should be. A post drafted in one does not draft in the other, and there is no unified inbox. For Australians who manage small brands across both platforms, the lack of genuine cross-app utility makes it harder to justify daily use of Threads.

This fragmentation matters more in Australia than in some other markets, because local creators lean heavily on Instagram as their primary storefront. Threads was supposed to give them a low-friction text channel that fed back into their main audience. Instead, it feels like a separate product that occasionally borrows Instagram's login.

What Australian users actually do on Threads

Despite the friction, Threads has carved out a quiet niche in the Australian social media landscape. Local journalists use it for breaking news commentary, often before pivoting to longer pieces on their own outlets. Federal MPs and political commentators in Canberra have adopted the platform as a sounding board, occasionally pivoting between Threads and X for different audiences. The result is a small but engaged user base that treats the platform more as a news desk than a personal network.

Consumer behaviour looks different again. Many Australians use Threads as a secondary feed, dipping in for trending topics like the Ashes, Australian Open tennis, or the footy finals before returning to Instagram for social browsing. The platform's tighter integration with Instagram's follower graph means Australian creators get a built-in audience they did not have to build from scratch, even if engagement rates remain lower than on the parent app.

The casual tone of Australian social media fits Threads reasonably well. Aussie users tend to favour dry, deadpan humour in short bursts, exactly the kind of content that performs well on a text-led platform. The threading model also maps neatly to live event commentary, where sports fans in Brisbane or Perth can hold parallel conversations during a State of Origin match or an AFL grand final.

What Meta should fix before the next wave of users arrives

For Threads to convert curious Australian newcomers into daily users, the next update cycle needs to land obvious improvements. Stable notifications, edit functionality, and proper drafts handling should be table stakes rather than roadmap items. Performance on mid-range Android devices deserves the same attention given to iOS optimisation. Deeper integration with the consumer devices Australians have already brought into their homes would also help the platform feel like part of a broader ecosystem.

The competitive pressure is real. Bluesky's Australian user count has been climbing steadily through 2024, driven by journalists and creators fed up with Meta's algorithmic unpredictability. Mastodon's decentralised model appeals to the privacy-conscious crowd that grew up watching the ACCC take Meta to task over data practices. Without significant rework, the Android client will keep behaving like a perpetual beta rather than a finished product, and Threads risks becoming another abandoned Meta experiment alongside the original Facebook Home and the much-lamented Facebook Poke.