The people behind third-party Twitter clients Tweetbot, Twitterrific, Talon, and Tweetings are warning users that their apps could lose important features like push notifications and an auto-refresh timeline in June. The problem is that after June 19th, Twitter will be removing the “streaming services” that have enabled developers to implement these functions in their apps.

Update 4:30PM ET: However, we don’t know exactly when this change will come. In response to the furor on Twitter, the company has announced it is “delaying the scheduled June 19th deprecation date.” In a thread, the developer relations account further said the company it “will provide at least 90 days notice from when the Account Activity API becomes generally available” and that “more specifics on timing [are] to come.”

Last year we announced our plan to retire Site Streams & User Streams, and replace them with the Account Activity API (currently in beta). We are delaying the scheduled June 19th deprecation date. — Twitter Dev (@TwitterDev) April 6, 2018

It’s good news that Twitter is backing down, but there are still open questions about whether its new Account Activity API is robust enough for third party Twitter apps to provide the same streaming services they now offer. So far Twitter hasn’t allowed outside developers to participate in the beta testing of that API. Even in a best-case scenario, it would only potentially restore the push notification side of things; it sounds like third-party Twitter clients just won’t have any practical way of offering a live-updating timeline anymore. “You will see delays in real-time updates during sporting events and breaking news,” the developers say.

I kind of doubt it. It’s hard to say without even knowing if we’ll get full access, partial access, have to pay for it, etc. but just from the way it works it doesn’t seem like it’d be enough to really replicate the full live stream experience. — Sean Heber (@BigZaphod) April 6, 2018

They’re raising the issue now in hopes that Twitter will offer some kind of solution. That’s probably only going to happen if the company hears enough complaints about yet another decision that, whatever the technical reasoning might be, will end up hampering the functionality and appeal of third-party Twitter clients.

Some of these apps offer native software on platforms that Twitter itself has decided to abandon. I myself am a user of Tweetbot on Mac, even if I generally stick with the official app on mobile. Jeff Seibert, Twitter’s former director of product, says it would be a “grave error” if the company does nothing.

While I deeply understand the complexities of running Twitter’s dev platform, and there are no easy decisions here, it would be a grave error to effectively end Mac support by killing Tweetbot. https://t.co/4ZcBRE80FQ — Jeff Seibert (@jeffseibert) April 6, 2018

The app developers are concerned that “many folks don’t realize that their favorite Twitter app is about to break, so awareness is the first step. Together, we may be able to get Twitter to constructively address this state of affairs before the June deadline.” If you want to sound off, @TwitterDev is the account to @. Or you can tweet your own thoughts with the hashtag #BreakingMyTwitter.

Original article updated to reflect Twitter’s new stance on the deprecation date.