<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:psc="http://podlove.org/simple-chapters" xmlns:podcast="https://podcastindex.org/namespace/1.0">
    <channel>
        <title><![CDATA[Foo’s Audiolog: Indie.am]]></title>
        <description><![CDATA[This is my personal audio blog!]]></description>
        <link>http://github.com/dylang/node-rss</link>
        <image>
            <url>https://api.indie.am/upimg/b11e828ca5c4c4dddc424e1d10a80318.jpg</url>
            <title>Foo’s Audiolog: Indie.am</title>
            <link></link>
        </image>
        <generator>Podcast for Node</generator>
        <lastBuildDate>Tue, 14 Apr 2026 22:00:03 GMT</lastBuildDate>
        <author><![CDATA[James Foo]]></author>
        <pubDate>Tue, 14 Apr 2026 22:00:03 GMT</pubDate>
        <copyright><![CDATA[2026 James Foo. All Rights Reserved.]]></copyright>
        <language><![CDATA[en]]></language>
        <webMaster><![CDATA[Indie.am]]></webMaster>
        <docs>https://indie.am/</docs>
        <ttl>60</ttl>
        <category><![CDATA[Society & Culture>Personal Journals]]></category>
        <itunes:author>Indie.am</itunes:author>
        <itunes:summary>This is my personal audio blog!</itunes:summary>
        <itunes:owner>
            <itunes:name>indie.am</itunes:name>
            <itunes:email>contact@indie.am</itunes:email>
        </itunes:owner>
        <itunes:explicit>false</itunes:explicit>
        <itunes:category text="Society &amp; Culture">
            <itunes:category text="Personal Journals"/>
        </itunes:category>
        <itunes:image href="https://api.indie.am/upimg/b11e828ca5c4c4dddc424e1d10a80318.jpg"/>
        <item>
            <title><![CDATA[Introducing the Indie.am PWA!]]></title>
            <description><![CDATA[<h1>My First Post Using the Progressive Web App (PWA) for In the AM</h1>
<p>Hello! This is my first post using the Progressive Web App (PWA) for In the AM. Over the past three days, I&#39;ve completely rewritten the old mobile app, which previously required a Twitter login. Now, it features a simple username and password login system while maintaining all the original functionality.</p>
<h2>Discovering Web APIs</h2>
<p>I was pleasantly surprised to find that many native APIs, which were once exclusive to iOS or Android, are now accessible through web APIs. Features like media session, play center, lock screen, and media controls are all available in a PWA.</p>
<h2>Improved Audio Capture</h2>
<p>In the past, capturing audio devices on mobile browsers or non-native apps was problematic. Building a Cordova app a few years ago involved dealing with cross-platform issues. However, now there are unified APIs for user media that work seamlessly across browsers in a PWA. Permissions are straightforward and effective, making the experience delightful.</p>
<h2>Transitioning from Native to PWA</h2>
<p>Rewriting the app was a rewarding experience, and I can&#39;t think of anything that isn&#39;t possible in the PWA today that was available in the native app. This post is made on a test account using the new username and password login. Previously, accounts were created using Twitter or Apple sign-in, which required an email address. This allows me to link old audio logs if the new sign-in methods aren&#39;t supported.</p>
<h2>Future Plans</h2>
<p>I&#39;m planning to explore Google and Apple login for the PWA. However, I&#39;m uncertain about implementing Apple login, as I haven&#39;t done it for a PWA before. I&#39;ll give it a try, and in the worst-case scenario, users may need to reset their passwords for the email accounts they used previously. This should enable them to access the new PWA.</p>
<p>Thank you for reading my first post using the PWA for In the AM!</p>
]]></description>
            <link>https://indie.am/foo/5a1211b86f562c31fce871ce269d0b83</link>
            <guid isPermaLink="true">https://indie.am/foo/5a1211b86f562c31fce871ce269d0b83</guid>
            <dc:creator><![CDATA[James Foo]]></dc:creator>
            <pubDate>Fri, 03 Jan 2025 00:00:00 GMT</pubDate>
            <enclosure url="https://api.indie.am/audiofile/foo/5a1211b86f562c31fce871ce269d0b83.mp3" length="1181209" type="audio/mpeg"/>
            <googleplay:owner>futhey@gmail.com</googleplay:owner>
            <googleplay:author>James Foo</googleplay:author>
            <googleplay:image href="https://fastly.picsum.photos/id/610/512/512.jpg?hmac=IY289W_0tTtj2i5inDU5I-z987D7Rcf8ZhwAUqCid3w">
            </googleplay:image>
            <itunes:author>James Foo</itunes:author>
            <itunes:subtitle>James Foo, Indie.am</itunes:subtitle>
            <itunes:summary>Hello, so this is my first post using the PWA Progressive Web App for in the AM. Over the past three days, I&apos;ve completely rewritten the old mobile app that you used Twitter login to use. username password login is simple progressive web app and managed to maintain all the functionality. I was really surprised a lot of the native APIs that used to be locked behind native iOS or Android API like your media session, your play center, your lock screen, media controls. All of those are available through web APIs now and to a P WA. Additionally, there used to be some problems with capturing audio devices on mobile browsers or non-native apps. There was a lot of jank cross-platform just for building a Cordova app a few years ago when I attempted it and now it&apos;s pretty nice unified APIs for user media that work across browsers in a PWA permission or nice and easy and they work. It was pretty delightful rewriting this and I can&apos;t think of anything that&apos;s not possible in the progressive web app today that was in the native app . So this is my first post on a test account using username and password login, email and password login, when each account was created using Twitter or Apple sign in, it required email address so I can link up those old audio logs if the new sign-in methods aren&apos;t supported. I&apos;m going to take a stab at Google and Apple login on the P WA but I&apos;m not really sure on the Apple side I have not implemented that for a PWA before. I will give it a shot though and in worst case scenario people may do password resets for the email account they used in the past and they should be able to use the new PWA. [BLANK_AUDIO</itunes:summary>
            <itunes:explicit>false</itunes:explicit>
            <itunes:image href="https://fastly.picsum.photos/id/610/512/512.jpg?hmac=IY289W_0tTtj2i5inDU5I-z987D7Rcf8ZhwAUqCid3w"/>
            <itunes:episodeType>trailer</itunes:episodeType>
        </item>
    </channel>
</rss>