I prepared a press release based on the main points from the 3.0 release notes. I tried my best making it press release-worthy ā although itās probably a bit on the lengthy side.
Note that it includes a mention of Freehive - I will check with them first if theyāre OK with us mentioning them here. Therefore please do not (yet) publicly use or distribute this article.
@ByteHamster As you can see, I dated the release for coming Wednesday. Do you think thatās realistic? I saw the update just went live to beta testers.
I donāt think there will be a single ārelease dayā. I plan to do a staged roll-out over a few weeks, and when it is at 100%, release on F-Droid. In the past, we received most bug reports not during the beta, but during the staged roll-out to production.
How about changing the opening Free to Open Source? Iām not sure if AntennaPod has a philosophical stand on the choice of word here, but I do think the suggested phrasing stands a higher chance to avoid making the very first word to cause the press release to be discarded.
Free podcasting app for Android AntennaPod adds new Home screen and gets brand refresh in 3.0 release
In the title, I keep reading the words Android and AntennaPod together (as though āAndroid AntennaPodā was the name of the app) and it doesnāt sound right.
It either needs a comma between the words:
Free podcasting app for Android, AntennaPod adds new Home screen and gets brand refresh in 3.0 release
or, perhaps better:
Free podcasting app AntennaPod for Android adds new Home screen and gets brand refresh in 3.0 release
UPDATE:
or, as has been done in the German version, use quotes:
Free podcasting app for Android āAntennaPodā adds new Home screen and gets brand refresh in 3.0 release
Assuming this is targeted towards non-users and outlets with limited space for external content, I find it a bit too long to be honest.
Also, some more specific feedback:
I find unusual periphrases such as āad-free and gratisā sound a bit odd. Canāt we just say āfree and open sourceā or āfree and without adsā, so readers know what weāre talking about?
I wonder if talking about a ābrand refreshā is a real selling point. My gut reaction as a non-user would be āGreat for them. And whatās in it for me?ā. Maybe just say ānew lookā or ānew designā?
I wouldnāt necessarily delve into explaining new features (such as the Home screen) in detail here. (see below)
Still with the aim of keeping this quick to read, perhaps some paragraphs could be replaced with bullet points?
Aside from this press release, in recent weeks I was thinking about a series of blog posts showcasing some advanced and non-obvious features that AntennaPod has gained in recent times. Perhaps the idea could be expanded to cover new features, even if they are very evident to users (e.g. the Home screen).
If there is interest, we can get a separate discussion started.
I didnāt want to focus āopen sourceā too prominent, because most regular Android (app) blogs/websites donāt know or care about this.
Yes, letās go for that.
I agree. Maybe your other suggestion can be a solution:
I love this, and have been thinking about this (specifically in the context of newly added features) myself. For the home screen I already started making some scribbles, which I can share in a new thread. Would you mind creating the new thread?
I thought of this as a solution to the length problem, because, with a dedicated blog post, we can cut those parts out and just add a link to the detailed description.
Fair point. Problem for the lead: āand without adsā isnāt an adjective that fits in the sentence. (As explained above, I donāt feel like going for āopen sourceā.) I went for āfree and ad-freeā.
Iāve not seen bullet points being used in press releases before, so I would be a bit wary of that. The shorter paragraphs should already help towards the āquick to readā goal.
I think itād be better as a blog post. It can be a nice place to explain how things works in the background. For example it would allow us to share that the āContinue listeningā excludes items which have a starting time of 00:00:00. Itās a bad example because I wouldnāt actually include this, but just to indicate that we can go more in-depth. Also it would have a more āsellingā than āexplainingā tone.
Thanks @keunes - you did! Just a final edit for grammar/clarity:
āan exercise led by the design companyā¦ā (if you want to include both verbs, I guess it should be āled and contributed toā? It doesnāt sound great though.)
Here comes the updated German translation - I left the date as āMarch 2023ā - we can update it later. It would be good if another German speaker could read through it
@ByteHamster I must admit that I donāt really know/remember what the motivation is behind the Manage downloads section (I noticed it was not in my initial mock-ups). So I just invented a reason, but if you have any better text for it, please let me know (same for any other text).
I have not explicitly requested permission, if thatās what youāre after. But given that the majority is open source and public broadcasters, combined with the fact that this is a one-off explainer and not standard promotional material (like the play store), I say itās fine to use.
Will do a french translation before tomorrow evening if no else does it before. Didnāt have much time before.
Is there a deadline?
I also think it doesnāt matter too much if press release is not converted for all languages. Itās often in news to have quoted info in English and the reviewer usually take excerpt and translate it. (Besides giving a link to the original source)
For the Google Play screenshots, a German public broadcaster denied my request to use their logo. Even a small science podcast told me that we can only show some of their episode covers because they already had problems with licensing. So for āofficialā screenshots (and I think a blog post is quite official), Iām a bit careful.
Not for now. We can only send it when v 3.0 is available on Google Play & F-Droid, and much depends on a) Googleās approval process (which seems to take quite a bit longer for now) and b) the number of new types of crashes weāre getting back from the slowed roll-out. Weāll mention it when we have a deadline in sight
Journalists (like anyone of us I guess) prefer to be ālazyā if they can be, so taking out one step in their process by providing a translation increases our chance of being picked up. But indeed, no need to get it in all languages. Based on this list of outlets that weāre trying to reach we identified FR, DE & IT as target languages for now.
Thatās what I was saying: having your work (as a āneutralā broadcaster) used in permanent promotion of a product (even if open source) is something else than being featured one time in a blog post or on social media in a product explainer. The exposure is much less (with it the chance of license issues) and the purpose/aim (with it the ādegree of associationā) is (slightly) different. Therefore I think weāre safe here.
(Happy to include my personal name, in case anyone ever complaints or makes a claim about this graphic they can point to me.)
