Archive for March 20, 2026

Friday, March 20, 2026

Overcast Transcripts

Marco Arment (Mastodon):

What’s in this beta:

  • Transcripts of most podcasts (swipe on the episode art during playback, it’s a new page past the info screen)

  • Live-scrolling of transcripts during playback

  • Tap to seek on any line of text

  • Music detection

All of this should work even with dynamic ad insertion… and even with private/membership podcasts!

And if you play an episode that isn’t transcribed yet, you can transcribe it right on your iPhone (if you’re running iOS 26+).

This is really impressive, and I think it will be transformative for podcast listening and triage. There’s a long discussion with more technical details in the latest Accidental Tech Podcast.

Christian Bender:

The way you can follow along as the audio plays, or jump to a place in the episode by tapping a paragraph in the transcript, is just so convenient. It made me seriously consider using Apple Podcasts. And of course, I immediately tested the Overcast implementation.

[…]

It’s the kind of feature that fits how I use podcasts. Like chapters, it supports choice. It lets you cut through the noise and get straight to the topics that interest you.

Previously:

Update (2026-04-10): Marco Arment (Mastodon):

The first update with transcripts is now in the App Store!

See also: Steven Aquino.

Android Sideloading Waiting Period

Ryan Whitwam (Hacker News):

With its new limits on sideloading, Android phones will only install apps that come from verified developers. To verify, devs releasing apps outside of Google Play will have to provide identification, upload a copy of their signing keys, and pay a $25 fee. It all seems rather onerous for people who just want to make apps without Google’s intervention.

Apps that come from unverified developers won’t be installable on Android phones—unless you use the new advanced flow, which will be buried in the developer settings.

[…]

Google swears it’s not interested in the content of apps, and it won’t be checking proactively when developers register. This is only about identity verification—you should know when you’re installing an app that it’s not an imposter and does not come from known purveyors of malware.

[…]

So a rootkit can be malware, but a rootkit you downloaded intentionally because you want root access on your phone is not malware, from Samat’s perspective. Likewise, an alternative YouTube client that bypasses Google’s ads and feature limits isn’t causing the kind of harm that would lead to issues with verification. But these are just broad strokes; Google has not commented on any specific apps.

Adamya Sharma (via John Gruber):

When Google execs previously said sideloading would become a high-friction process on Android, they really weren’t kidding.

The company is finally sharing what Android’s new sideloading flow will look like in practice, and if you’re someone who installs apps outside the Play Store, you’re going to feel it immediately, and you’re going to feel it deeply.

[…]

It’s a deliberately slow and almost impossible-to-rush-through process that will allow advanced Android users to sideload apps from unverified developers, while giving them plenty of caution to keep them safe from malicious apps and bad actors.

[…]

Yes, really. There’s a mandatory one-time, one-day waiting period before you can proceed and sideload an app from an unverified developer. Google calls it a “protective waiting period.”

Horrific. Can we finally dispense with this notion that Apple’s App Store can be as restrictive as they want because if you don’t like that you can just buy an Android phone?

tavavex:

The part in the flow where you select between allowing app installs for 7 days or forever is a glimpse into the future. That toggle shows the thought process that’s going on at Google.

I can bet that a few versions down the line, the “Not recommended” option of allowing installs indefinitely will become so not recommended that they’ll remove it outright. Then shrink the 7 day window to 3 days or less. Or only give users one allowed attempt at installing an app, after which it’s another 24 hour waiting period for you. Then ask the user to verify themselves as a developer if they want to install whatever they want. Whatever helps them turn people away from alternatives and shrink the odds of someone dislodging their monopoly, they will do. Anything to drive people to Google Play only.

Gregory:

At this point I’m convinced that there’s something deeply wrong with how our society treats technology.

Ruining Android for everyone to try to maybe help some rather technologically-hopeless groups of people is the wrong solution. It’s unsustainable in the long run. Also, the last thing this world needs right now is even more centralization of power.

Previously:

Update (2026-03-26): Peter N Lewis:

Just so it’s clear, because it’s frequently not been clear in reporting I’ve seen, the 24 hour waiting period is after turning on the switch that allows sideloading. It is not before each individually sideloaded app.

And I can sort of see their reasoning on this, to defend naive users from being conned in to turning it on. For savvy users, you can just turn it on, wait a day and then get on with your life.

Saagar Jha:

My security hot take for this week is that Google’s changes for sideloading on Android seem to strike a good balance between security and usability. This gives me hope the team is putting thought into maintaining the original dream of the platform rather than making a worse iOS.

Of course the jury is still out on how well this will work but the rationale seems pretty solid to me. Being tricked into installing blatant malware is, despite how you might feel about it, a major problem for Android. Historically efforts to combat this have badly hurt openness.

The general problem with security is identifying bad things is hard because often it will end up impacting desirable things too. In this case Google picks a very specific quality of scams and aims to target it specifically: urgency. I expect this to be very high signal!

Update (2026-03-30): Stephen Schenck (Hacker News):

Users will be able to opt out of further delays after that initial 24 hours.

Today Google clarifies that this status can carry over to new devices, so you only ever have to go through it once.

Updates to Vibe Coding Apps Rejected From the App Store

Hartley Charlton:

Apple has quietly blocked AI “vibe coding” apps, such as Replit and Vibecode, from releasing App Store updates unless they make changes, The Information reports.

[…]

Apple told The Information that certain vibe coding features breach long-standing App Store rules prohibiting apps from executing code that alters their own functionality or that of other apps.

[…]

An Apple spokesperson said the policy is not targeted specifically at vibe coding apps.

If the apps are in breach of longstanding rules, why is it the updates that are blocked? It seems like either Apple should have rejected the apps long ago or else they’re trying to retcon the new policy, which remains unclear to me.

Malcolm Owen (9to5Mac):

Report sources say that the apps in question are close to being approved for the App Store again, but after agreeing to make changes to the way they function. These changes include updating previews of the vibe-coded apps, or removing functions like making apps specifically for Apple devices.

That sounds like removing the core functionality.

The report adds that there are other apps that exist in the App Store that didn’t get the same limitation, such as Vercel’s v0. Other apps that offer similar capabilities that aren’t coding-specific, such as design app Canva, could potentially be hit by the same issues, since they can be used to create filters, quizzes, and other items using AI.

For the most part, the report focuses on the issue being one of competition and revenue protection. Apple could lose revenue due to these vibe coding apps creating software that doesn't pass through the App Store itself.

Previously:

Update (2026-04-01): Juli Clover (Hacker News):

Apple has removed a “vibe coding” app from its App Store, reports The Information. AI app building app “Anything” was pulled from the App Store , and Anything co-founder Dhruv Amin was told that his app violated Guideline 2.5.2.

[…]

“Anything” launched on iOS back in November with no issue, and Amin says the tool has been used to publish thousands of apps in the App Store . The app let users create and preview vibe code apps on the iPhone, and it raised $11 million at a valuation of $100 million back in September.

While Anything was removed from the App Store on March 26, Apple has been blocking updates to the app since December. Amin submitted an update that would allow vibe coded apps to be previewed in a web browser instead of in the app to attempt to comply with the 2.5.2 rule, but Apple blocked the update and pulled the app.