![]() ![]() That would have let me keep the old version. This really should have been a paid update, with a new app. However, since all of the key functions are now buried 2 to 3 layers deep, I guess we'll all be looking at the UI for much longer, and might as well make it look pretty since we'll be spending 2 to 3x more time in the app getting it to the things it used to do in 1/3 the time. If the thing I'm noticing is the kerning, then your book is not engaging me and/or your typography is distracting. If I am admiring your UI, you're doing it wrong. Regarding the large chunk of the blog post that discuses bringing the UI feel closer to iOS 10, my response is that a good UI should not be noticed. And it really just seemed like the developer had to lower the UI down to the lowest common denominator of users because they couldn't figure out how to use it. This may be an enormous improvement for that functionality, but I can't speak intelligently since I'm not the target market.Īs I read the blog post, I started to get infuriated, which is just to show how much I loved this thing before this week. The developer would know, since he is the expert in the field. Perhaps there's a lot of demand for people chain-listening to shorter podcasts. I can't tell you what the next podcast I'll want to listen to after that, in 4 days is. So if I start a 3 hour podcast right now, I won't finish it until 3 or 4 days from now. Also, I generally listen to one podcast across multiple sittings. I've never had to build a playlist around that, since it's not a big deal to manually select another podcast every 2 to 3 hours on average, and to be frank, I don't know what I'll want to listen to in 3 hours. The podcasts I listen to are generally 1 to 4 hours long per episode. I can't speak intelligently about this, as I have never used it, and no desire to do so. The blog post mentions what seems like improvements to que/playlist functionality. I had zero problem doing those things before, and everything was right there immediately available. Seeing information about the podcast episode The following tasks now take 2 to 3 additional taps/clicks/swipes: But unfortunately, the exact opposite direction of what makes sense to me. I've spent the last 10 minutes reading his blog post. It still might be a lot of work, depending on your infrastructure and codebase.If you would leave a great app over these really thoughtful changes, I don't know what to tell you. I say this because it's a server-side change that doesn't require rolling out a new version of your app. ![]() This is akin to the difference between someone reading an article on your blog vs someone subscribing to your blog's RSS feed. The stat that matters to podcast advertisers is downloads/listens, but subscribers matter to podcast creators because subscribers form a base for future growth. Breaker is now reporting, albeit in a different format.Castro doesn’t want to give us inaccurate data.Please report podcast subscribers in your crawler’s user agent string. It will be so glorious!īut it starts with you, dear podcast app creator. Maybe podcasting platforms like Transistor, Fireside, and Anchor will bake reporting right in. If/when there’s a critical mass of podcast apps reporting, we can start building open source tooling around this data so more podcasters can benefit. So, here is my request to all podcast apps that have their own crawler: please follow Overcast’s lead and add subscriber count to your user agent string! It’s a relatively small 2 investment that will yield an outsized proportion of goodwill coming your way. It’s super useful information to have! How cool would it be if we could have the same information for every popular podcast app?! I’ll tell you: too freakin’ cool We extract this count and store it locally so we can track subscribers 1 over time. Overcast’s feed crawler has a small feature that adds tremendous value to podcasters like us: it reports your subscriber count in its user agent string: Overcast/1.0 Podcast Sync (8462 subscribers feed-id=484679 +)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |