<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>Accrescent Blog</title>
        <link>https://blog.accrescent.app/</link>
        <description>See Accrescent blog posts and announcements.</description>
        <generator>Hugo -- gohugo.io</generator><language>en-US</language><lastBuildDate>Tue, 25 Nov 2025 00:00:00 &#43;0000</lastBuildDate>
            <atom:link href="https://blog.accrescent.app/index.xml" rel="self" type="application/rss+xml" />
        <item>
    <title>Accrescent and Android Developer Verification</title>
    <link>https://blog.accrescent.app/posts/android-developer-verification/</link>
    <pubDate>Tue, 25 Nov 2025 00:00:00 &#43;0000</pubDate>
    <author>Logan Magee</author>
    <guid>https://blog.accrescent.app/posts/android-developer-verification/</guid>
    <description><![CDATA[<p>Google <a href="https://android-developers.googleblog.com/2025/08/elevating-android-security.html" target="_blank" rel="noopener noreffer ">recently announced</a> that starting next year, Android will require all apps to be registered
by verified developers for users to install them on their devices, i.e., all apps must be registered
by a developer who has performed identity verification with Google or else they won&rsquo;t be installable
on <a href="https://www.android.com/certified/partners/" target="_blank" rel="noopener noreffer ">certified Android devices</a>. While users have asked us about this new requirement (specifically
about how it affects Accrescent), we have been waiting to provide an official response until more
information became available. Now, although we are still waiting on Google to provide more details
on how the program will work in the context of third-party app stores, we have enough information to
explain how it will affect Accrescent and how we are responding to the change.</p>]]></description>
</item>
<item>
    <title>A Road Behind, A Road Ahead</title>
    <link>https://blog.accrescent.app/posts/road-behind-road-ahead/</link>
    <pubDate>Tue, 11 Nov 2025 00:00:00 &#43;0000</pubDate>
    <author>Logan Magee</author>
    <guid>https://blog.accrescent.app/posts/road-behind-road-ahead/</guid>
    <description><![CDATA[<p>Three months ago, we published an update on our development progress as well as our <a href="../progress-update-and-roadmap#roadmap" rel="">roadmap</a> for
the next three months and beyond. Now that those three months are over, we want to share the
development progress we&rsquo;ve made in that time, the impact it has on Accrescent going forward, and our
next priorities as we shift into a new development cycle.</p>
<h2 id="progress-update">Progress update</h2>
<h3 id="app-store-api">App store API</h3>
<p>The first task on our roadmap was developing and migrating to the <a href="../progress-update-and-roadmap#the-directory-service" rel="">directory service</a>, or as we now
refer to it, the app store API &mdash; a massive overhaul to how Accrescent finds apps, calculates app
compatibility, fetches app information, and checks for updates. This task has been completed
successfully, and while it took longer than expected to implement, we believe that taking the
additional time necessary to implement it correctly has resulted in a robust solution that is
well-designed and built to last long into Accrescent&rsquo;s future.</p>]]></description>
</item>
<item>
    <title>Progress Update and Roadmap</title>
    <link>https://blog.accrescent.app/posts/progress-update-and-roadmap/</link>
    <pubDate>Mon, 11 Aug 2025 00:00:00 &#43;0000</pubDate>
    <author>Logan Magee</author>
    <guid>https://blog.accrescent.app/posts/progress-update-and-roadmap/</guid>
    <description><![CDATA[<p>In our <a href="../the-future-of-accrescent" rel="">recent post</a> about Accrescent&rsquo;s financial future and sustainability, we <a href="../the-future-of-accrescent/#through-the-looking-glass" rel="">announced</a> that to
build trust and transparency with our community, we&rsquo;d be publishing a follow-up blog post about what
we&rsquo;ve been working on lately and where we&rsquo;ve been setting our sights, i.e., what our roadmap is.
This is that post.</p>
<p>If you haven&rsquo;t already read our <a href="../the-future-of-accrescent" rel="">post about Accrescent&rsquo;s future</a>, we highly recommend reading
through it for context. <strong>The items planned on our <a href="#long-term-roadmap" rel="">long-term roadmap</a> cannot be accomplished unless
we reach our <a href="../the-future-of-accrescent/#where-were-at" rel="">funding goal</a></strong>, so any time you spend reading or sharing our post is deeply
appreciated.</p>]]></description>
</item>
<item>
    <title>The Future of Accrescent</title>
    <link>https://blog.accrescent.app/posts/the-future-of-accrescent/</link>
    <pubDate>Mon, 04 Aug 2025 00:00:00 &#43;0000</pubDate>
    <author>Logan Magee</author>
    <guid>https://blog.accrescent.app/posts/the-future-of-accrescent/</guid>
    <description><![CDATA[<p>Accrescent is a novel Android app store focused on security, privacy, and usability. We&rsquo;ve been
building Accrescent since 2021 to improve the security and freedom of everyday Android users by
providing an alternative to Google Play which doesn&rsquo;t compromise on technical excellence and
protecting our users. Aligned with this mission, over 42,000 people worldwide trust Accrescent to
deliver their apps safely. Now, we need your help to continue.</p>
<p>Accrescent has always been free to use because we believe security shouldn&rsquo;t have to come at a
price. We also understand we&rsquo;re trusted by our users to secure a sensitive and significant portion
of their lives &mdash; the apps they use &mdash; so we&rsquo;ve built Accrescent transparently, <a href="https://github.com/accrescent" target="_blank" rel="noopener noreffer ">making our code
open source</a> so others can run and inspect it as they please.</p>]]></description>
</item>
</channel>
</rss>
