u/Knuckleclot

hey everyone, i’m building an ios app called logly and i’d love some positioning/marketing feedback.

the app started as a simple ai food tracker:

write what you ate like a note
→ get estimated calories/macros
→ track your day

but ai calorie tracking is getting crowded fast, so i’m trying to make the stronger angle about the full progress journey.

logly tracks:

food logs
calories/macros
water
weight
body measurements
progress photos
timeline entries
shareable progress cards

my thinking is:

food logging is the input, but progress is the reason people come back.

most ai calorie apps focus heavily on the meal/photo/estimate. i’m trying to position logly more as “ai food logging + visual progress journey”.

would love feedback:

is this positioning clear?
would you lead with ai food logging or progress journey?
does the journey feature make the app feel more differentiated?
what would you test in the first app store screenshots/ad creatives?

video uses demo data/photos to show the flow.

check it out here:
https://apps.apple.com/mk/app/ai-food-tracker-logly/id6759680382

hey everyone, i’m building a food/progress tracking app and i’ve been working on the progress side of it.

the idea is that it shouldn’t only be about calories. users can also track their journey over time with weight, measurements, progress photos and timeline entries.

i’m trying to make it feel motivating without making it feel toxic or too focused on before/after photos.

would love some honest feedback on the flow/design:

does the timeline make sense?
would it be better to keep photos and measurements together or separate?
does anything feel cluttered?
would this kind of feature actually help users stay consistent?

screenshots use demo data/photos just to show the flow.

Hey everyone, I’ve been building Logly, an AI food and progress tracker for iOS.

I recently redesigned the onboarding to make it feel smoother and less overwhelming for first-time users. The goal is to explain the value quickly: write what you ate, get calories/macros estimated, then track weight, measurements, water, and progress over time.

I’d really appreciate feedback on:

- does the onboarding feel too long?
- is the value clear in the first few seconds?
- would you show the paywall before or after the first AI food log?
- anything that feels too generic or not native enough?

Not trying to spam, just looking for honest feedback from other Expo devs.

hey everyone, i’m the solo dev of saasclash, a startup-themed pbbg where you grow a saas company, compete on leaderboards, unlock cosmetics, and play through seasonal resets.

season 2 just went live, so everyone starts fresh.

i added a new leveling system, 7-day quests for new players, ui/ux improvements, optimizations, balance changes, and better cosmetics/profile stuff.

would really appreciate honest feedback from people who play pbbgs. mostly curious if the first session makes sense, if the progression feels clear, and if the rewards make you want to keep playing.

link: https://saasclash.xyz

hey guys, i’ve been building an ai food/progress tracker in expo and finally got the onboarding to feel decent

recorded a quick video of the flow. it asks for goal, weight, activity, nutrition focus, optional apple health, then shows the users starting targets

would love honest feedback on the ux

does it feel too long?
does the copy make sense?
does it feel smooth/premium enough?

stack is expo, react native, typescript, convex, revenuecat

I recently launched Speaksure, an app that helps people practice speaking out loud before interviews, meetings, presentations, or difficult conversations.

The idea came from a simple problem: most people read interview tips or write notes, but they rarely hear themselves answer out loud. Then in the real moment they ramble, use filler words, speak too fast, or sound less confident than they actually are.

Speaksure gives users short speaking drills, then scores the answer on clarity, confidence, conciseness, pacing, structure, and filler words. It also gives a sharper version of the answer so the user can practice improving it.

The app is free to download with daily practice included. Pro unlocks unlimited drills, custom scenarios, deeper coaching, and progress tracking.

App Store:
https://apps.apple.com/app/id6763595902

I’d appreciate any feedback on the positioning, App Store page, screenshots, pricing, or launch strategy.

I launched a small iOS app called Speaksure.

It is an AI speaking coach for short practice reps. You record an answer, get feedback on clarity, confidence, filler words, pacing, and structure, then see a sharper version of your answer.

I’m mainly trying to make it useful for people preparing for interviews or meetings.

I’d appreciate feedback on:

- whether the App Store screenshots explain the app clearly

- whether the first session feels useful enough

- what would make you trust an app like this

Not trying to spam. I’m still improving the product and would genuinely appreciate feedback.

Hi everyone,

I built this landing page for my app Speaksure and I’d love some honest UI/UX feedback.

The app helps people practice speaking out loud for interviews, meetings, presentations, and everyday communication. After a practice drill, it gives scored feedback and a sharper version of the answer.

I’m mainly trying to figure out if the landing page communicates that clearly.

Things I’d love feedback on:

Does the first section make sense within a few seconds?

Is the headline clear enough?

Do the phone mockups help or distract?

Does the page feel polished and trustworthy?

Is the CTA too salesy or okay?

What would you change visually?

Here’s the page:

https://www.speaksure.app

Thanks in advance. I’m still improving it, so honest criticism is welcome.

I just launched my first iOS app and I’m working on improving the landing page before sending more traffic to it.

The app is Speaksure, a speaking coach for people who want to sound clearer in interviews, meetings, public speaking, and pressure moments.

The main user journey is:
landing page → understand value quickly → click App Store → try one short drill

I’d love UX feedback on:
- whether the page communicates the value clearly
- whether the CTA placement makes sense
- whether the sections answer enough objections
- whether the App Store click feels natural
- what might stop someone from downloading

Website: https://www.speaksure.app

I’m open to direct criticism. I want to make the page convert better, not just look nice.

I just got my first Expo app approved on the App Store.

It’s called Speaksure, a speaking coach app for practicing interviews, meetings, public speaking, and difficult conversations. Users record short answers and get feedback on clarity, confidence, pacing, conciseness, filler words, and a sharper version of what they could have said.

Stack:

- Expo / React Native

- TypeScript

- Convex

- RevenueCat

- App Store IAP

- AI/transcription pipeline for feedback

The review process took a couple tries.

First rejection: my custom microphone permission screen had a button that said “Enable microphone.” Apple wanted neutral wording like “Continue” before the native permission prompt.

Second rejection: subscriptions loaded fine for me in TestFlight, but Apple’s review environment showed the plans as loading indefinitely. I had to make the fallback state safer and verify the RevenueCat/App Store Connect setup.

Biggest lesson: make permission and purchase flows review-safe, not just user-friendly on your own device.

Still a lot to improve, especially onboarding and retention, but seeing it live in the App Store feels great.

Just got my first iOS app approved and ready for distribution.

It’s called Speaksure, a speaking coach app that helps people practice interviews, meetings, public speaking, and difficult conversations. You record a short answer, get feedback on clarity, confidence, pacing, conciseness, and filler words, then see a sharper version of what you could have said.

The review process took a couple of tries. The first rejection was because my custom microphone permission screen had a button that said “Enable microphone.” Apple wanted neutral wording like “Continue” before the native permission prompt.

The second issue was with subscriptions not loading properly in the review environment, even though they worked in TestFlight. I improved the fallback state, verified RevenueCat/App Store Connect setup, and resubmitted.

Biggest lesson: App Review is not just about whether it works on your device. The review environment can expose edge cases you don’t see locally.

Still a lot to improve, especially onboarding and retention, but seeing “Ready for Distribution” feels great.

Happy to answer anything about the review process, RevenueCat setup, or Expo/React Native side.

i’m working on the onboarding for speaksure, an ios app that helps people practice interviews, meetings, pushback, and difficult conversations.

the user records a short answer, gets feedback on delivery, and sees a sharper version they can model next time.

i recorded the onboarding flow and skipped the diagnostic step to keep the video short.

would love feedback on:
visual hierarchy
copy clarity
pacing
whether the value is obvious before the user reaches the first drill

just submitted my expo app to app store review

been building a speaking coach app called speaksure with expo/react native. the app lets you practice interviews, meetings, pushback, and difficult conversations, then gives feedback on clarity, confidence, pacing, filler words, and how to say the answer better next time.

finally submitted the first ios build for review today.

the hardest parts were honestly not the ui, but getting the production build stable:

- eas env vars

- convex config

- revenuecat products

- oauth / email otp

- app store metadata

- privacy labels

- screenshots

expo was solid overall, but production builds definitely expose everything you ignored during dev.

curious for people who have shipped expo apps: what usually caused your first app store rejection or review delay?