<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Untold</title>
    <description>The latest articles on DEV Community by Untold (@untold_app).</description>
    <link>https://dev.to/untold_app</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4135822%2F5745ff40-9068-4ff0-be27-6e0bb380f3be.png</url>
      <title>DEV Community: Untold</title>
      <link>https://dev.to/untold_app</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/untold_app"/>
    <language>en</language>
    <item>
      <title>Building Untold: designing an anonymous support app around trust boundaries</title>
      <dc:creator>Untold</dc:creator>
      <pubDate>Mon, 21 Sep 2026 13:12:27 +0000</pubDate>
      <link>https://dev.to/untold_app/building-untold-designing-an-anonymous-support-app-around-trust-boundaries-4mb7</link>
      <guid>https://dev.to/untold_app/building-untold-designing-an-anonymous-support-app-around-trust-boundaries-4mb7</guid>
      <description>&lt;p&gt;Untold is an anonymous mental-health support app we’re building for RevenueCat Shipaton 2026. The difficult part is not only matching two people; it is making the trust boundary understandable enough that someone feels safe starting a conversation.&lt;/p&gt;

&lt;p&gt;A few decisions we made:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The app works signed-out by default. Sign-in adds sync; it is not required to start.&lt;/li&gt;
&lt;li&gt;Journals are server-readable under tight access control for premium insights, so we do not claim end-to-end encryption.&lt;/li&gt;
&lt;li&gt;The product is designed around leaving, reporting, and control rather than a public feed, follower graph, or profile.&lt;/li&gt;
&lt;li&gt;The stack is Flutter, FastAPI, Supabase, and RevenueCat.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The lesson so far: every privacy sentence that is stronger than the implementation becomes marketing debt. We are documenting the limits plainly and using feedback to improve the onboarding and trust flows.&lt;/p&gt;

&lt;p&gt;Try the current build: &lt;a href="https://untold.dpdns.org/" rel="noopener noreferrer"&gt;https://untold.dpdns.org/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I’d value feedback from other builders on the onboarding, report/leave flow, and whether the trust model is clear from the first screen.&lt;/p&gt;

&lt;h1&gt;
  
  
  showdev #flutter #supabase #buildinpublic
&lt;/h1&gt;

</description>
      <category>buildinpublic</category>
    </item>
  </channel>
</rss>
