Arif — first off, thank you. Genuinely. Feedback this detailed, from someone who's actually been following along and testing things, is worth its weight in gold. Most people don't take the time. You did, and a bunch of these are going straight onto our list.

One thing that'll come up a lot below, so I'll say it up front: our north star is parity with FluentCommunity on the web. Most of our users specifically want the app to feel like their site, not a separate product — so when FC does something a certain way, we tend to mirror it. Where we can make something optional without breaking that for the parity crowd, we're always happy to look. And if you ever want to go completely off-script, that's exactly what the dev bundle (full source) is for — more on that at the end.

1. Feed layout. We actually ship three feed views today — Card, List, and Timeline — modeled on the FC mobile web experience, which is what most of our users ask us to match. That said, a full-width feed as an option is very reasonable: the folks who want web-style cards keep them, and people who want the X/Facebook feel can switch. If you've got a screenshot or specific example of the layout you're picturing, drop it in — helps us build the right thing instead of guessing.

2. Create Post button. Funny enough, we originally had the composer at the top of the feed just like FC web, and moved to the floating action button after people asked for it. So you're both right — which tells me the real answer is to make it a choice. We'll look at offering both.

3. Post composer polish. Happy to — but I need a little more to go on. Right now it matches FC's own mobile web composer pretty closely, so "awkward" could mean a few things. If you can point at what specifically feels off (spacing? the flow? a particular field?), ideally with a screenshot, we'll dig in.

4. Sort by → For You / Following. The sort options aren't ours — they come straight from FluentCommunity and its API. We support the full set FC offers: New Activity, Latest, Oldest, Popular, Likes, Alphabetical, Unanswered, and Following. A "For You / Following" tab layout like X is really a FluentCommunity UI decision — if FC built it that way on the web, we'd mirror it in the app with full parity. So that one's honestly best raised with the Fluent team directly. (And with the source code, you can build the feed however you dream it up.)

5. Google Sign-In. On our radar. Our approach with anything in the Fluent family — FluentAuth, Fluent Messaging, Fluent Cart — is to build core support for it, and we've already started on FluentAuth. So a social login option is something we'd love to bring as a core module. The module system is also open, so the community and other devs can build their own social login modules too — exactly what it's designed for.

6. Bare-bones comments. Totally get the instinct — clean, simple comments do feel more natural for a social feed, and I don't disagree. Here's the honest tradeoff, though: the formatting in comments isn't something we bolted on for its own sake. FluentCommunity on the web already lets members format their comments — bold, italic, and the rest — natively. We layered headings on top of that in the app, but the basic formatting is baked into FC itself. So even if we stripped the app's comments down to plain text, a member could still post a formatted comment from the web and it'd show up that way in the app — because that part's out of our hands. We can look into letting the admin hide the feature in the app from your users, but again they'd still have some formatting options on web unless you hide it there as well.

7. Custom CSS & JS. Great one to unpack, because it gets at what the app actually is. Ours is a fully native React Native app — real native screens, not a webview or a wrapper around your site. CSS and custom JS are web technologies; there's no webpage under the hood for them to style. What we do respect is FluentCommunity's native theming — set your accent color, logo, and site name in Fluent, and the app picks all of it up automatically, light and dark.

If what you're really after is "my site's exact CSS/JS carried into an app," that's closer to a PWA — a wrapper around your website. Different product category, and the tradeoff is you lose the speed and feel of a true native app. We went native on purpose, because that's the experience most communities are missing.

And this is where our two products matter: on the managed app we keep it clean, fast, and native, so it won't pick up site CSS by design. But the dev bundle ships you the entire source code. You could restyle it top to bottom, wire in anything you want — turn it into a talking-dinosaur UI if that's your thing. It's yours. So "respect my customizations wherever possible" is basically unlimited on the dev side — it's just done in native React, not CSS.

8. User profile. I'd love more detail here. We keep profiles in native parity with the FC website so they feel consistent, and I don't want to drift too far from that core — but "more premium" can mean a lot of things. What would make a profile feel premium to you? Specific elements, a layout you've seen elsewhere, the cover-image behavior? The more concrete, the better, and we can look at offering layout options.

9. Leaderboard. Totally with you. We'd love to add the core FC leaderboard and it's on the list. In the meantime — most of our own users run their leaderboard through GamiPress, so we already ship a full GamiPress leaderboard integration. But we hear you on native FC leaderboard support for folks on FC's built-in one, and we'll work on it.

On pricing — I want to spend a minute here, because I think our model is genuinely different from anything else in this space, and it's easy to read it through the lens of how everyone else prices these things.

First, a clarification: we're not trying to sell to all 12,000 FC users — that's kind of the point. We have two very different products for two very different people.

The managed app ($33/mo) is for someone who wants a clean, fast, native app for their community and doesn't want to deal with builds, store submissions, or updates — we handle all of that, on your accounts. It's for a smaller set of sites we work closely with. And even here: everything is built on your store credentials, under your name. Stop paying and you don't lose the app — it stays live on your accounts, you just stop getting updates. Compare that to BuddyBoss or Appzap, where you're paying hundreds a month and the app disappears the day you stop.

The dev bundle ($449, full source, one-time) is really for people managing their own clients, or anyone who wants total control. One license per client, you own it outright, and you charge your clients whatever you want.

And on $449 being "as affordable as possible" — I'll gently push back, because I think it's already doing something nobody else does. That's the entire source code to a production native app. No one in this ecosystem hands that over — it would blow up their own business model. BuddyBoss, Appzap, the rest: at best you get a few hooks to tweak things around the edges, usually at a premium, and never the actual source. We give you all of it. That's not us pricing high — it's us handing you the keys to the whole car for what others charge for a look under the hood.

So I'd flip the framing: the reason we can keep it this accessible is because we're not trying to be a 12,000-seat SaaS. We built these tools so communities never have to be locked into those monthly models again — full ownership, your accounts, your code. That freedom is the product.

Anyway — this is exactly the kind of feedback that makes the app better, so thank you again for taking the time. Keep it coming, especially screenshots on the layout and profile stuff. And when you're ready to grab it, we'll be here.

Hey Arif — quick follow-up on this, because a few of the things we talked through have actually shipped since.

Feed layout — you can now choose full-width (edge-to-edge, the X/Facebook feel) alongside the boxed card view. Admin sets the default, members can switch it on their own phone — exactly the "keep parity for the folks who want it, optional for everyone else" approach we discussed.

Create-post button — we did make it a choice, like we said we would. You can now pick a compact round + button, an inline composer pinned to the top of the feed (FC-web style), or the full-width bar. Both of the options you and others asked for, side by side.

Leaderboard — Fluent Community's native leaderboard is now in the app too: a real screen plus a home widget, with each member's own points, level and rank. (So that's the FC one now, in addition to the GamiPress integration we already had.)

They're all in the latest app version, 1.4.0 — update from the Play Store and you'll see them. Still chewing on the rest of your list; this was just the first wave. Thanks again for the nudge on these.