Salaam! This is my first time posting here, thought I'd share a prayer time app that I've built a couple months back. It's called apta, which stands for "another prayer time app."

I made it as I wanted a lightweight prayer time app that wasn't bloated with ads and popups.

It's free and currently iOS only. There are also widgets (both lock and home screen) and an Apple Watch app.

The app has a $1 optional one-time purchase to unlock some features in the Watch app and unlock background colors.

Would love for you all to try it out and I'd appreciate any feedback!

App Store: https://apps.apple.com/us/app/apta-prayer-times/id6760022766

Jazakallahu khayran!

Building the app was only half of it

Around one month ago, I launched my first app on both the iOS App Store and Google Play Store.

I had no idea how app launches worked, what Apple and Google would ask for, how long approval would take, or what kind of numbers would be considered “good” for a first app. I wanted to share some early numbers and lessons from the process, in case it benefits someone else.

Apple App Store experience

Signing up for the Apple Developer Program costs $99/year.

My experience with Apple was actually easier than I expected. I knew Apple was strict with the approval process, and I expected to spend a while fixing things before the app would be accepted, but in the end the process was quite straightforward.

I signed up for the Apple Developer Program and submitted the app on 15 May.

The next day, on 16 May, the first version was not accepted immediately. Apple asked for more information, including things like a screen recording, tested devices, the app’s purpose, target audience, instructions for using the main features, external services used, and whether there were any regional differences.

At first, it felt like a lot, but looking back, it made sense. Apple did not only want to know whether the app worked. They wanted to understand what the app does, who it is for, how it works, and whether everything is properly explained.

After I fixed the missing details, the app was approved on 18 May, and it became available on the App Store on 19 May.

One thing that surprised me was that after Apple approved the app, it still did not appear properly in all regions at first. I later realized there were still agreements and terms I had to accept in App Store Connect. Some were related to countries, laws, regulations, distribution, and App Store terms.

So one lesson was:

An app being approved does not always mean your developer account is fully ready.

You also need to check agreements, terms, privacy policy, support links, copyright/content information, and all required documents.

After the first approval, Apple updates were usually smooth. Most reviews were completed within 24–48 hours.

Overall, Apple felt strict but polished. App Store Connect was confusing at first, but after learning it, it became quite straightforward. Apple’s analytics also feel detailed and fairly up to date. I could usually see data up to around the last 24 hours.

Google Play experience

Signing up for a Google Play Developer account costs $25 once.

The account fee is cheaper, and updates after launch are much faster, but the initial publishing process was more complicated for me because I was using a personal developer account.

For new personal developer accounts, Google requires closed testing before public release. In my case, Google specifically guided me to run a 14-day closed test with at least 12 users.

My Google Play Console identity verification was completed on 14 May.

I shared the first testing link on 15 May, had enough testers by around 17 May, and after the testing period, production access was granted on 1 June. That same day, the app launched publicly on Google Play.

So the Google timeline was roughly:

• 14 May — identity verified
• 15 May — testing links shared
• 17 May — enough testers reached
• 1 June — production access granted
• 1 June — public launch

Google felt slower at first because of the testing requirement, but much faster after launch.

Usually, after uploading an update to Google Play, it can become available in around one hour. With Apple, each update goes through review again and usually takes 24–48 hours.

Google Play analytics felt more delayed, sometimes by around 3–4 days, which made it harder to know what was happening after sharing or promoting the app.

So my experience was:

Apple was faster to launch once the documents were fixed, but slower for updates.

Google was slower to launch for a new personal account, but faster for updates after production access.

Early numbers

The app launched on the iOS App Store on 19 May 2026.

Exactly one month after launch, it had:

• 150 first-time downloads
• 9 five-star reviews

It launched publicly on the Google Play Store on 1 June 2026.

As of 22 June, it had:

• 79 downloads
• 7 five-star reviews
• 1 three-star review

The three-star review affected me more than I expected, to be honest. Not because I think everyone has to give five stars, but because when you build something with sincere intention, make it free, remove ads and subscriptions, and try to create something beneficial, even one lower rating can feel a little personal.

But I think that is also part of releasing something publicly. People will experience your app in different ways. A feature you spent the most time developing might be overlooked or even disliked, while something you did not prioritize much might become one of the things users appreciate most.

And that is something you often only discover AFTER publishing, no matter how prepared you think you are.

How I promoted it

I did not have a big launch campaign, and I did not have any real experience with promoting apps. I shared it in different Discord servers, a couple of subreddits, with family and friends, and made a few TikTok and social media videos.

The app itself is polished, and I honestly think it has more features and a better UI than some competing apps. But one thing I learned is that building a good app is not enough. You also need to know how to present it, explain it, and market it.

Right now, I feel like the biggest bottleneck is not the app itself, but my own ability to market it properly.

Screenshots and product pages matter more than I expected

One thing I underestimated was how important the product page is.

Before launching, I was mostly focused on the app itself. But when you publish on the App Store or Google Play, the product page becomes the first impression. For many people, it decides whether they download the app or ignore it.

You need good screenshots, clear text, and a page that quickly explains why someone should care.

The screenshots are also not as simple as just taking random screenshots from your phone. You need to prepare them properly, with the correct sizes, dimensions, and formats for each platform. Apple and Google both have their own requirements, and if the screenshots are the wrong size or do not clearly show the app, it can slow you down or make the product page weaker.

I also learned that screenshots are not only technical requirements. They are marketing material. They should show the best parts of the app, explain the value quickly, and look polished. A good app with weak screenshots can easily look less serious than it actually is.

This is something I would put more effort into earlier next time.

Final thoughts

I am still learning, and I am not sure how to judge the numbers yet.

The app has now passed 300 total downloads, which I am grateful for, but I also realize that a polished app does not automatically reach people. Distribution, presentation, screenshots, product pages, and marketing matter a lot.

One personal thing I noticed during this launch is how much my own perfectionism affected the process. I hold my work to a very high standard. Small details that many people might overlook can bother me a lot, and I often spend more time than necessary trying to polish things that others may not even notice.

That can be time-consuming, but I also see it as one of my strengths. When I take responsibility for something, I want it to be done properly and to the best of my ability.

At the same time, launching an app publicly teaches you that perfection is not really the finish line. You can polish something for a long time, but once it is public, people will still experience it differently. Some will love it, some will have criticism, and some may notice things you never expected.

If you are planning to launch your first app, especially as an independent developer, I hope this gives you a more realistic picture of what the early stage can look like.

I built Azimuth, a native, privacy first prayer app for Android, iPhone, iPad, and Mac.

Prayer times are calculated on your device, the app doesn’t collect personally identifiable data, and it only requests the permissions it needs.

Built with Kotlin + Jetpack Compose on Android and Swift 6 + SwiftUI on Apple platforms, Azimuth includes prayer reminders, a Fajr alarm, widgets, a Qibla compass, rakat guides, multiple calculation methods, madhabs, and high latitude support.

There’s no subscription. You get a 14 day free trial, then it’s a one time purchase if you decide to keep it.

I’d really appreciate any feedback. If you enjoy it, a rating or lifetime purchase helps support future development.

Android: https://play.google.com/store/apps/details?id=com.mirroredabstraction.android.azimuthcompass

Apple: https://apps.apple.com/ca/app/azimuth-prayer-times-qibla/id6781444202

Al-salam alaikum!

I spent a lot of hours driving every day, and I wanted to use that time toward Quran hifz. But every Quran app needs you to tap the phone screen, which is the last thing you should do at the wheel.

So I built QuranCar. You can split the Quran into small chunks (you pick the surahs and ayahs per chunk) and repeats each one until it sticks. Everything runs through CarPlay, so you control it with your steering wheel buttons, all while your eyes are on the road.

It works fully offline, and has no accounts, ads, or tracking. Free on the App Store: https://apps.apple.com/us/app/quran-audio-car-play-memorize/id6743359098

I'm building this solo and would love any feedback, especially from anyone who memorizes on their commute. Jazakom Allah Khair.

Assalam ahlikoum,

I would like to know if ayat boxes coordinates for Hafs tajweed mushaf are publicly available ? And if yes where can I find them? See the attached picture if my demand is not very clear 😅

Baraka Allahou fikoum

AoA,

I am the founder of an Islamic app called Qurb which helps Muslims build a daily quran reading habit by blocking their selected apps. I have built this as I saw this concept in other niches and found it interesting and useful for myself.

Now, since this is a consumer app, it requires a lot of volume for growth. Based on my research, social media marketing is the best approach for growing consumer apps.

Has anyone of you successfully grown a consumer mobile app, if yes what worked? Any advice would be helpful.

Also, do try out the app and give me feedback if you liked/disliked anything!

JazakAllah.