u/CvsBurak

Hi everyone,

I’d love to get feedback on my iOS app, Acheli: Voyage.

The app helps travelers turn flights, road trips, and train trips into shareable travel memories. You can create animated route stories, generate AI travel visuals, make boarding pass-style flight cards, save road/train trip stories, and track visited places on a travel map.

Main features:

  - Animated route stories for trip collections

  - Shareable AI-generated travel visuals

  - Boarding pass-style flight memories

  - Road trip and train trip story cards

  - Travel map with visited cities and pins

  - Destination weather and local info

  - AI destination chat for travel ideas

  - Achievements and travel progress

I’m especially looking for feedback on:

  - Is the app’s purpose clear from the first few screens?

  - Do the AI visuals and route stories feel useful or just nice to have?

  - Is the app too crowded with features?

  - Does the App Store page explain the value clearly?

  - Anything confusing in onboarding or navigation?

App Store link: https://apps.apple.com/tr/app/acheli-voyage-trip-planner/id6762149348

Thanks for any honest feedback. I’m actively improving the UX and App Store page.

Hi everyone,

I recently launched my first version of Acheli: Voyage, an iOS travel app I’ve been building.

The idea is simple: you add a flight, road trip, or train trip, and the app helps turn it into a visual travel memory. It can create route-based stories, boarding pass-style cards, travel map pins, and AI-generated travel visuals based on your start city, destination, trip type, date, and weather.

It also includes an AI destination chat for things like city tips, food ideas, places to visit, and trip planning.

I built it because I wanted something more visual than a normal trip planner, but more personal than just saving screenshots or notes. The app is still early, so I’d really appreciate feedback from travelers, frequent flyers, road trip people, or anyone who likes sharing travel memories.

App Store: https://apps.apple.com/tr/app/acheli-voyage-trip-planner/id6762149348

If you try it, I’d love to know:

  - Does the travel story idea make sense?

  - What feels confusing?

  - What would make it more useful before or during a trip?

Thanks for checking it out.

I’m working on improving my App Store page and I keep seeing mixed opinions about screenshot text.

Some people say you should avoid putting too much text on screenshots because users don’t read it and it makes the page feel crowded. Others say screenshots need short captions because people may not understand the app from UI alone.

I’m trying to find the balance.

My app has visual features, so I want the screenshots to show the actual UI clearly, but I also want users to quickly understand the value. I’m thinking short benefit-focused captions instead of long explanations.

For example:

  - Turn trips into stories

  - Create AI travel visuals

  - Map every journey

  - Plan with destination AI

Do you think App Store screenshots perform better with almost no text, or with short captions? How much text is too much in your experience?

I keep running into this problem while building my app.

Sometimes a new feature makes a lot of sense on paper. It solves a real use case, it fits the product, and I can clearly see why users might want it. But once it is added, the app starts to feel more complicated, more crowded, and harder to explain.

I’m also noticing that many users don’t really read instructions or follow guided flows. If something is not immediately obvious, they may miss it completely. That makes me question whether the feature is actually bad, or whether I’m just not designing the UX well enough.

So I’m curious how other indie devs handle this:

• How do you decide when a feature is worth adding versus when it just adds complexity?
• Do you have a rule of thumb for keeping an app focused while still improving it?
• And can you check this app and give me the feedback if its overcrowded or its simple to use and understand: Acheli Voyage Trip Planner

I just ran into something I didn’t even know was possible in App Store Connect and I’m trying to understand what happened.

I had an app with auto-renewable subscriptions and in-app purchases. Both the app version and the subscriptions were submitted together, and initially everything was in “Ready to Submit”.

The app got rejected for an unrelated reason. I fixed it and resubmitted a new version.

Here’s the weird part:

• The app got approved and is now live on the App Store
• But my subscriptions got rejected separately
• Result: the app is live, but in-app purchases don’t work at all

I always thought Apple required the first subscription to be approved together with the binary. Apparently not?

Now I’m stuck with:

• A live app
• Broken purchase flow
• Subscriptions in rejected state

So I have some questions:

How is it even possible for Apple to approve the app but reject the subscriptions tied to it?
Is this expected behavior or just reviewer inconsistency?
What’s the cleanest fix here — just resubmit the subscriptions alone, or do I need to push another app version?

The app's name is Acheli: Voyage check it on appstore.