#flutterflow

Project Verity || Development Log 📂

[Status: Early Architecture/ UI Design]

Welcome to the official Devlog for Project Verity.

The Mission

Project Verity is a clinical-first mobile application designed for high-volume tracking of dissociative states, complex symptoms, and identity data. I’m building this app to fill gaps left by Simply Plural and Octocon shutting down.

The system community is currently stuck with tools that are either Discord bots, entirely offline, and/or restricted to specific devices (like Android-only). Project Verity aims to be the cross-platform middle ground.

First and foremost, this is a replacement for the tools the DID/OSDD community is losing. Secondarily, but with equal importance, it is built as a general symptom tracker for those with Chronic Illnesses, acknowledging the massive overlap between these communities.

Project Verity is also explicitly Anti-Endogenic in stance, and recovery-oriented. Endogenic systems are not backed by medical science and they have their own apps. Whilst I cannot control who uses my app and I do not particularly care if any Endogenic system uses it; Endos, please do not expect to find validation of your existence either on this blog or on the app itself when finished enough to release. I am filling the need for a dedicated space that prioritises medical accuracy and clinical standards where other tools do not. This is not an invite to debate or to send threats/harassment in my ask box. This is simply the statement of a fact: the traumagenic system community and the chronically ill community, and especially those that sit in the middle, need a space that prioritises medical accuracy and care where other spaces cater to those that may not need that.

Meet The Developer

Helloooo tumblr. I’m Varian (He/They), a 20 year old no-code beginner developer living with disabilities and chronic illnesses, navigating my own complex health journey. I’m building this app as I saw a vacuum in the community for a reliable symptom/state tracker.

Whilst not a system myself, I spent a lot of time in the DID community as a teenager when figuring out my own mental health, and still do today due to having system friends. I also have disabilities/conditions such as BPD, Diabetes, AuDHD, and other physical disabilities that would benefit me to track.

The recent shutdowns of Simply Plural and Octocon and concerns I have seen online have made me realise how little resources there are for systems to track alters, especially so in a medical-first space. Additionally, I myself prefer the tools Simply Plural and Octocon provided me, as someone with chronic disabilities and illnesses, to inform my friends and family about what physical and mental state I am in; but using these tools often felt like intrusion into spaces not meant for me. By building my own app that is meant to serve both purposes, I seek to eliminate the feeling of intrusion into spaces not meant for non-systems and provide an inclusive space for those that need clinical aid.

One thing I will warn about: this is a potential project. I am the only dev, and ADHD and my other issues means work happens in bursts when my health, focus, and personal life allow. The goal is a finished app, but please view this as a “live build”. It may take a long time, and I’m learning as I go, and working with what Flutterflow has to offer. Comments, suggestions, and feedback help keep my ADHD brain engaged, focused, and keep the momentum moving. Don’t be afraid to say hi or drop some suggestions/feedback in my ask box! In fact, dropping some suggestions about what you might have liked from Simply Plural/Octocon, or wanted but they didn’t have, would be great for me to build off of! :)

I will add to this post in the future when I am certain of more aspects of my app!

Hot take: calling FlutterFlow a "no-code platform" does it a disservice. And it sets teams up to fail.

Here's the actual setup. FlutterFlow is a visual development platform built on top of Google's Flutter framework. When you drag a widget onto the canvas, it's generating real Dart code underneath. You can export that code, open it in VS Code, and keep building in pure Flutter.

That's not no-code. That's visual-first development.

Why does the label matter? Because "no-code" sets the wrong expectations. People think they can skip architecture planning. Skip security. Skip device testing. Then they're shocked when their app gets rejected from the App Store or crashes on older phones.

What Actually Ships

A.B Money, built on FlutterFlow, hit 250,000 users and $100K+ in revenue. Built in under 2 months. Grupo Purdy, an enterprise automotive company, cut app delivery time by 80%.

Both treated the platform as a productivity tool, not a shortcut around engineering.

The Honest Math

Traditional mobile dev: $40K to $500K+, 4-12 months

FlutterFlow builds: $5K to $60K, 2-8 weeks

Cross-platform Flutter: 30-50% cheaper than native iOS + Android separately

The savings are real. They exist because you're not manually coding every UI screen, every Firebase call, every routing transition. You're building on top of generated code and focusing human time on the parts that need human judgment.

What You Still Need Humans For

Data schema and architecture planning

Security rules (Firestore/RLS, API key management, input validation)

Performance tuning (image compression, lazy loading, caching)

Custom Dart code for anything the visual builder can't express

Device testing on actual hardware, not just the in-platform preview

App Store and Google Play deployment with all the guidelines that go with it

This is why FlutterFlow works best with developers who understand mobile, not non-technical users trying to skip the learning curve.

The Quick Framework

Is FlutterFlow right for your project?

Yes: MVPs, business apps, marketplaces, content platforms, internal tools, anything with standard CRUD patterns

No: Games, 3D rendering, heavy video processing, complex Bluetooth protocols, on-device ML

Everything else lives somewhere on that spectrum. The Empiric Infotech team wrote up the full decision framework plus a 7-step production build process here: how to ship production-ready FlutterFlow apps.

Worth reading if you're planning a build in 2026. The 30-item pre-launch checklist alone is the part most tutorials skip entirely.

Reblog Hook Version (optional shorter repost)

If you want a shorter Tumblr-style follow-up post a week later:

FlutterFlow is reshaping the app development landscape with powerful no‑code tools that balance simplicity and functionality. 🌐 From integrated backend support to fast prototyping, this platform helps startups and enterprises bring ideas to life quickly and efficiently.