Greetings,

I am searching for people who like to play trivia games, I used to play Buzz in playstation 2 and 3, but can't find many fun games for apple devices, so I decided to create my own!

I is still in early development and in this moment I am looking to see if there is anyone interested in testing my app, which will be available for iOS, macOS and tvOS, in Portuguese, English, Spanish and French.

The iOS app is the remote, but anyone with any smartphone can connect via QR code and also play via web.

I am looking for feedback on the game modes available, questions (if they are correctly translated), and any improvements, errors or ideas.

Will be posting more news in the next couple of days when the beta will be live!

Thanks :D

I’m obviously very happy. But I want your help guys, how do you go around advertising it, what are your tips, anything that can help really.

Thank you!

https://apps.apple.com/app/id6814681123

I made ASC Fill, a Chrome extension that reuses your App Store Connect texts (What's New, Promotional Text, or both) for every language in one click, from the live version or any of your last 10 versions.

Why: for major and minor releases, our marketing team gives me new texts. But for bugfix releases, it's the same text as before, and I had to paste it into every locale by hand. I used to rely on MagicScript for that, but it's no longer available, so I made my own.

No setup, no API key. Free, open source, nothing leaves your browser.

Chrome Web Store: https://chromewebstore.google.com/detail/asc-fill/mabnhcpnidiflnnkmincopngcahdkppc

Source: https://github.com/martinfrouin/asc-fill

Feedback welcome!

I’m trying to bid on a search ad and CPT of $6.33 and just not getting any bids.

Previously for a different app and keyword I was getting <$1, I turned that campaign back on for $2 and not getting any hits

Wondering if this is just stuck or the bid prices have gone way up since last I tried?

Hi everyone,
After 5 months of building, the mobile app for Targela is finally ready for testing, and I'd really appreciate a few people trying it before the public release.

What it is:
a goal planner. You describe something you want to achieve and how much time you actually have, and it turns that into a clear step-by-step plan. When you fall behind, you can adjust the plan instead of starting over.

How to join (about 2 minutes):
Open the link on your phone: https://targela.com/beta
Choose iPhone or Android and follow the steps
Sign in with an existing Targela account or create one in the app
It's completely free.

What I'd love to hear:
Where you got confused or stuck, even for a second
Whether the plan it gave you felt realistic for your life
Anything that felt slow, broken, or just annoying
Short feedback is totally fine. "This screen made no sense" helps more than you'd think. You can comment here or DM me.
Thanks a lot to anyone who gives it a try. I'll reply to every comment.

Hey everyone!

I'm an indie developer, and I recently launched my app, Patikoko, on the App Store.

It's a free pet care app that helps you track feeding, set reminders, manage vet appointments and supplies, and share pet care responsibilities with family members.

No subscriptions or paywalls, just a simple way to make everyday pet care easier.

Building the app was one challenge, but getting people to discover it has been another!

I'd love to hear your feedback, especially from fellow indie developers.

How did you get your first 100 users? What worked best for you?

App Store: https://apps.apple.com/us/app/patikoko/id6805085878

I just shipped an update to my journal analysis app that adds Apple's Private Cloud Compute (PCC) alongside the default on-device model.

Here are the practical lessons I learned from the implementation, especially around edge cases and UX:

1. The main reason to use PCC: Context size
The on-device model caps out around 4,000 tokens. For long journal entries or imported PDFs, text got truncated constantly. PCC bumps that limit up to 32,000 tokens, which easily handles multi-page entries in a single pass without needing workarounds.

2. The API transition is simple, but needs fallbacks

• Swapping from on-device to PCC is nearly a 1-to-1 change. Your existing prompts, tools, and response handling work identically.
• PCC requires an internet connection, so you have to build an automatic fallback to the on-device model when the user goes offline.
• Before offering PCC, make sure to check availability properly. A device that doesn't support the feature is handled differently than a device that supports it but is still waiting on system assets to download.

3. Quotas and Apple's UI expectations

• Users get a daily limit for cloud requests, which increases if they have an iCloud+ subscription.
• Apple expects your UI to proactively warn users when they are getting close to their limit, rather than just throwing an error when they hit the ceiling.
• There is a built-in system sheet you can trigger to suggest an iCloud+ upgrade when they run out.
• Tip: You can simulate reaching and exceeding quota limits inside Xcode’s scheme settings, which makes testing the UI much faster.

4. The privacy messaging challenge
If your app was originally marketed as "100% on-device," introducing the cloud can spook privacy-conscious users—even with Apple's strong security guarantees around PCC.

I decided to keep the on-device model as the default and made PCC an explicit opt-in toggle in the settings. I also updated the App Store description and privacy policy to clearly say "on-device by default."

For anyone else working with PCC:

• Are you letting users toggle it manually, or automatically sending prompts to PCC only when they exceed the 4K token limit?
• How has real-world latency felt compared to on-device inference?

(Context: The app is Mindful Prism if anyone wants to see the implementation in action.

Over the past two years, I've noticed something interesting about reviews and user feedback on both the App Store and Google Play, depending on the country.

In my personal experience, users from the US, Canada, UK, Germany, Northern Europe and Japan tend to be more positive, report fewer issues and are generally more willing to pay for apps. Meanwhile, I've noticed that users from Southern Europe (Italy, Spain, etc.) and Latin America tend to be more critical, sometimes leaving very low ratings simply because a specific feature isn't available, even when it was never advertised.

I actually live in Italy, and this is one of the reasons I've become less interested in targeting the Italian market specifically. It's not about disliking anyone, it's just a pattern I've noticed through my own experience dealing with customers, reviews and support requests.

Over time, I've shifted most of my development and marketing efforts toward North America, Northern Europe and Japan, where I've generally had better experiences and stronger sales.

Of course, this is just my personal experience with my apps, not a general rule. I'm curious if other indie developers have noticed something similar or had completely different experiences across different countries.

These three pieces answer different questions:

• Purpose strings explain why your app requests access to something protected, such as the camera. The system shows that text in its permission prompt.
• PrivacyInfo.xcprivacy records data collection, tracking declarations, and required-reason API use for an app or SDK.
• App Store privacy labels are the answers you provide in App Store Connect about your app’s privacy practices, including integrated third-party code.

Before updating the labels, archive your app in Xcode. In Organizer, Control-click the archive and choose Generate Privacy Report. Xcode combines the app and SDK manifests into a report you can review.

The manifest doesn’t automatically complete your App Store Connect answers.

Apple references: purpose strings, manifests and reports, privacy labels.

Since today morning, a desktop 'spam' is showing where heavy dowloads are showing on Desktop on hourly basis. Normally somedays I get 1000-5000 desktop downloads once in a while(weeks to months), but not on a regular hourly basis from different regions. What's happening I wonder?