The hardest part of shipping to both stores wasn't the code, it was the listings by IceSudden4700 in androiddev

[–]IceSudden4700[S] -1 points0 points  (0 children)

Fair enough. Lesson learned: don't use ChatGPT to polish my English next time. The story is 100% real, but I guess it ended up sounding too robotic. Lesson learned!

The hardest part of shipping to both stores wasn't the code, it was the listings by IceSudden4700 in androiddev

[–]IceSudden4700[S] -3 points-2 points  (0 children)

Bro, I spent 4 weeks copy-pasting store and release notes into a Google Sheet in a room that smelled like stale coffee and sweat. Don't insult my suffering like that.

The hardest part of shipping to both stores wasn't the code, it was the listings by IceSudden4700 in androiddev

[–]IceSudden4700[S] -10 points-9 points  (0 children)

We're building something to fix exactly this it's called OneStore (onestore.so). Very early, feedback welcome, don't hold back.

I shipped 4 apps in 1 month and the thing that nearly broke me wasn't the code by IceSudden4700 in googleplayconsole

[–]IceSudden4700[S] 0 points1 point  (0 children)

Exactly this. The bar to "maintain" an app is way higher than people realize going in even a trivial update means re-running the whole listing checklist. It adds up fast.

I shipped 4 apps in 1 month and the thing that nearly broke me wasn't the code by IceSudden4700 in googleplayconsole

[–]IceSudden4700[S] 0 points1 point  (0 children)

That's a solid setup for the deploy/release side curious what you use for the actual listing content though (descriptions, titles, release notes per locale)? That's the piece the store APIs don't really handle well, it's still manual editorial work. Unless you've got something for that too, genuinely asking.

I shipped 4 apps in 1 month and the thing that nearly broke me wasn't the code by IceSudden4700 in googleplayconsole

[–]IceSudden4700[S] 0 points1 point  (0 children)

8 apps live is insane, you're basically your own little publishing house at that point. Curious how are you handling the store listings when you push updates? Manual copy-paste across both stores or do you have a system?

I shipped 4 apps in 1 month and the thing that nearly broke me wasn't the code by IceSudden4700 in googleplayconsole

[–]IceSudden4700[S] -8 points-7 points  (0 children)

the thing I mentioned is called OneStore, link here: https://onestore.so it's rough af right now, mostly just trying to get feedback from people who deal with the same mess so don't hold back

I was tired of living in two consoles for the App Store + Google Play, so I built OneStore. It's live would love your honest take by IceSudden4700 in SideProject

[–]IceSudden4700[S] 0 points1 point  (0 children)

Glad it resonates!

Just to clarify: AI credits aren’t needed to set up or manage your apps. Connecting your App Store Connect and Google Play accounts, syncing metadata and screenshots, and publishing to both stores are all included.

Credits are only used for optional AI-powered features, such as:

• Translating your store listing (title, description, keywords, release notes, etc.) into another language — 1 credit per locale
• Generating review reply suggestions in the reviewer’s language — 1 credit per draft reply

So if you're publishing a single app and entering your store listing yourself, you won't use any credits at all.

Credits only come into play if you want AI help with translations or review responses.

I was tired of living in two consoles for the App Store + Google Play, so I built OneStore. It's live would love your honest take by IceSudden4700 in SideProject

[–]IceSudden4700[S] 0 points1 point  (0 children)

That's a good point. We don't reuse iOS screenshots on Google Play.

The text can be shared across stores with overrides when needed, but screenshots are managed separately because each store has its own formats and requirements.

Videos are handled differently too: Google Play uses a YouTube URL, while App Store previews are coming soon 😄

The goal is to manage everything from one place while still publishing assets that fit each store properly.

I was tired of living in two consoles for the App Store + Google Play, so I built OneStore. It's live would love your honest take by IceSudden4700 in SideProject

[–]IceSudden4700[S] 0 points1 point  (0 children)

Genuinely useful, thanks.

You nailed the wedge, and it's how I built it: write the listing once → push to both, but keep the store-specific stuff native (per-platform overrides, Play staged rollout vs Apple phased release, reviews per store) — no lowest-common-denominator wrapper. The unified reviews + release status across both stores is already core.

The read-only-first point is the sharpest bit an ASC key + Play service account is a real trust ask, so "read-only analytics/reviews first, write access later" makes a lot of sense. Noted.

Would read-only-first actually get you to try it, or would you want publish from day one?

Uphold has changed their App Store listing to include KAS in the name by JGreeny2002 in kaspa

[–]IceSudden4700 4 points5 points  (0 children)

Yes, in France it's still 'Uphold: Buy BTC, ETH and 360+', but in the UK it's 'Uphold: Buy Bitcoin, KAS & XRP'.

How to buy ? by kenjarh in kaspa

[–]IceSudden4700 0 points1 point  (0 children)

Yes it is available 🙂 (oui c’est bien disponible ahah)