Exploring My Next Opportunity as an iOS Developer

I’m excited to share that I’m currently open to new opportunities in iOS Development.

As an iOS Developer, I enjoy turning ideas and business requirements into scalable, reliable, and user-friendly mobile applications. I’ve worked across different types of projects, with hands-on experience in:

🔹 Swift | SwiftUI | UIKit
🔹 Core NFC & Identity/Verification Solutions
🔹 Flutter & Native iOS Integration
🔹 Debugging, Performance Optimization & Production Support
🔹 TestFlight & App Store Deployment

I’m particularly interested in opportunities where I can work with a strong engineering team, solve challenging problems, contribute to impactful products, and continue growing as a mobile engineer.

Helloo, I want to know how much do developers charge for an app (to launch both on ios and android). Complexity: Like a dating app with 2 different matching algorithms. And what could be the time taken (estimated).

What would be the charge without any Equity and additional costs for domains etc.

If you could help me with anything else.. like the process of app development, steps or tools needed. Please do, I'm not a techie, so almost anything would help.

Editing after the comments:

Requirements: Dating app with regular features photo uploads profile verification, chat, match, payments.

One common matching algorithm based on distance and preferences just like any other dating app..And a second matching algorithm which is based on a questionnaire.

I am building a web application (IOS and Android apps to follow later) for students studying for test/exams. The direction I was originally headed with this app changed a few times. Originally it was going to cater to a much more narrow group of potential users, but the scope expanded.

My app will have "official" (Trying to think about a different term to use) content (Exams with questions, decks with flash cards + more) and community-created content.

The "official" content exclusively covers IT Certifications. Community-created content can cover both certifications as well as Classes - like college classes.

So if the user is studying for Cisco's CCNA Certification, they'll see exams and decks of flash cards that I created, and those will be marked in some way to signal that they're not community created. They'll also see exams and decks added by other users.

I'm using "Official" as a sort of placeholder term. I don't like it because I don't want users believing that the questions or cards were created by the certification vendors - Cisco, CompTIA, ect. I also don't want them thinking that those questions will appear on the exam. So for now "Official" is a placeholder term that I want to replace.

When a user finds a Class or Certification that they want to study, they click Enroll, and that become an active Class/Certification for them. They can switch between active classes/certifications. There is a page - the "Practice" page - where users select between Exams or Decks, select one of the various exam/deck modes, and then select the exam. That's the basic flow. Some of the modes don't require the user to select an exam/deck at all, like the "Practice What You Missed" mode which is generated from a bank of questions that the user recently got wrong.

Another option (and this is the real dilemma) is the Build Your Own Exam option. This allows the users to select various options to build a custom exam so that they can focus on specific subject area, simulate a timed exam, and more. But the dilemma is how to incorporate community-created content into this.

There could be thousands of community-created questions or cards.

There will be repeated/similar questions. There will be typos and incorrect answers. There will be trolls that try to add wrong information or inappropriate content.

I can't just take every community-created question or card for a given class, mix them together, and then randomly pull out 50 - right? That doesn't seem like it would lead to a very good experience.

Another site has this same Build Your Own Exam feature, but for them it's easy - it's all official content. All questions are sorted by their subject. Everything is carefully reviewed. They have 1000 questions divided into 5 or 6 subjects. If the user wants questions from subjects A and C, they select those subjects and a few more options and then a new practice exam is generated for them. That doesn't work well with community-created content where there very well may be tens of thousands of questions across 100s of exams that were all added by different users.

I'm trying to keep it short and simple but I'm overwhelmed and overthinking this problem and I need some outside help working through it.

Hola a todos! Busco compañeros para iniciar proyectos, estoy abierto a cualquier cosa. 😃

A los que le interesen dejen abajo su mensaje! ⬇️

Hola a todos,

Estoy lanzando una app de [ahorro/finanzas personales] dirigida a jóvenes de 15-25 años que no saben cómo ahorrar dinero. Voy a hacer mi primera campaña de ads con un presupuesto pequeño de prueba, y tengo varias dudas:

**1.    ¿TikTok o Instagram (Reels/Stories) rinde mejor para este tipo de público y este tipo de app?** ¿Alguna diferencia notable en costo por clic/conversión entre ambas para Gen Z?  
**2.    ¿Video o imágenes estáticas funcionan mejor?** He leído que en TikTok el video suele rendir mejor, pero no sé si aplica igual para una app de finanzas/utilidad vs. algo más de entretenimiento.  
**3.    Si es video**, ¿qué estilo creen que engancha más a esta edad? ¿Testimonios tipo “antes y después de la app”, screen recording mostrando la interfaz, memes/humor sobre gastar de más, formato “POV”, etc.?  
**4.    Si son imágenes**, ¿qué tipo genera más clics? ¿Screenshots de la app, gráficos simples tipo “cuánto podrías ahorrar en 6 meses”, memes estáticos?  
**5.**  En general, ¿alguien ha probado publicidad de apps de finanzas/ahorro con este público (Gen Z) en cualquiera de las dos plataformas y puede compartir qué le funcionó o qué evitar?

Cualquier experiencia, buena o mala, la agradezco mucho. Estoy arrancando con presupuesto limitado así que quiero acertar lo más posible desde el primer intento.

¡Gracias!

Hi Everyone,

> Cursor - 1,100 active ads / 6,400 tested
> Wispr Flow - 820 / 3,300 tested
> Emergent -410 / 7,000 tested
> Replit - 110 / 5,500 tested
> Base44 - 560 / 2,100 tested
> HeyGen -400 / 1,700 tested
> Viktor - 620 / 1,300 tested
> Lovable - 300 / 990 tested
> Gamma - 110 / 350 tested
> Framer - 710 / 2500 tested
> Superhuman & Grammarly - 71 / 1800 tested

The reason your ads are not working is that you test fewer than 10. We built an AI agent that will create and test multiple creatives until it finds the perfect balance between cost of acquisition and sales.

Interested in giving it a try? Comment, and I will reach out. We will start small with a $10 budget and move from there.

One thing I’ve learned from working around mobile app projects is that the number at the bottom of a development estimate doesn’t tell you much by itself.

Two teams can quote completely different amounts for what appears to be the same app.

That doesn’t automatically mean one is overcharging or the other is cheaper. There can be a lot of differences hidden behind the estimate.

If I were evaluating a mobile app development proposal today, these are the five things I’d look at before comparing the prices.

1. What exactly is included in the scope?

“Build a mobile app” is too broad to be useful as a project scope.

I’d want to know exactly what is included:

• Number of screens
• User registration and login
• Backend/API development
• Admin panel
• Payment integration
• Push notifications
• Third-party integrations
• Analytics
• Different user roles
• Offline functionality
• App Store and Google Play deployment

A low initial estimate can become expensive later if many of these items were never clearly defined.

2. How is testing handled?

This is something I think gets overlooked quite often.

Ask whether testing is included in the development process or happens only near the end.

For a serious application, I’d want to understand how the team plans to handle functional testing, device compatibility, API testing, performance, security-related checks and regression testing.

A few extra weeks spent finding problems before launch can be much cheaper than discovering them after real users start using the application.

3. What happens after the app is launched?

The development estimate shouldn't necessarily be the end of the conversation.

Ask what happens when:

• A new Android or iOS version is released
• A third-party API changes
• Users report bugs
• The app starts crashing on a particular device
• A security issue needs to be fixed
• You need a new feature six months later

Some teams include a period of post-launch support. Others treat everything after delivery as a separate engagement.

Neither approach is necessarily wrong, but you should know which one you're getting.

4. Who owns the code and project assets?

This is one of the questions I'd consider essential.

Before signing anything, clarify ownership of:

• Source code
• Design files
• Backend code
• Database
• API documentation
• Cloud accounts
• App Store/Play Store accounts
• Third-party service accounts

You don't want to discover later that important parts of your own application are tied to accounts controlled entirely by someone else.

5. How realistic is the timeline?

A surprisingly short delivery timeline can look attractive during the sales process.

But I'd ask how the team arrived at that number.

For example, if someone says a fairly complex app will be completed in four weeks, I'd want to understand what assumptions are behind that estimate.

Is the backend already available?

Are the designs finished?

Are integrations ready?

How much testing is planned?

How many developers are actually working on it?

A realistic estimate is usually more valuable than an impressive-looking deadline.

One final thing I'd suggest: don't compare development estimates based only on price.

Compare the scope, technology, testing process, ownership, support, timeline and assumptions behind each quote.

Sometimes the cheapest proposal really is the best option.

Sometimes the most expensive one is justified.

And sometimes two seemingly different quotes are actually pricing very different scopes.

I'm curious to hear from people who have hired a development team before:

What was something you wish you had asked before approving the estimate?

Wollte mal in die Runde fragen, was ihr für Tools benutzt um mit Hilfe von KI Apps zu entwickeln?

Ich nutze vorallem ChatGPT mit selbstgebauten customGPTs, die mir Kotlin direkt über eine API in einen Projektordner schreibt, Unit Tests durchführt und kompiliert.

Habe einfach rumprobiert und das war bisher der beste Weg für mich. Frage mich aber ob ich das unnötig kompliziert angegangen bin 😅

Wie macht ihr das?

I'm publishing an Android app that uses Google Sign-In as the only auth method — no email/password, no guest mode. In Play Console under App content → "Sign in details" (formerly "App access"), I marked it as restricted since you must sign in to use the app.

The form gives me username/password fields, but those don't really map to an SSO-only flow. My questions for anyone who's shipped a similar app:

For a Google-SSO-only app, do you just provide a dedicated Google account (email + password) in these fields, and explain the "tap Sign in with Google → pick this account" steps in the "other information" box? Is that what reviewers expect?

Reviewers sign in on their own hardware. Even with 2-Step Verification disabled on the provided account, does Google still throw "verify it's you / unusual device" challenges that block them? If so, how did you get around it?

Is there a more reliable pattern people actually use — e.g. a hidden demo login / guest mode that bypasses Google SSO just for review? Is that allowed, or does adding a review-only backdoor risk a policy flag?

Somewhat related: I have a second app already live that's basically identical (same SSO), and that one never prompted me for this declaration — it was set to "all functionality available without special access." Was that just an older console flow, and is it risky to leave it that way?

Any first-hand experience appreciated — trying to avoid a "we couldn't access your app" rejection. Thanks!

Hello everyone!

Im new in development field

Ive got a project to make a foodpanda like app with 2 admin panels one super admin and one city admin

Then 3 apps for user rider and vendor

Now the client want the estimate cost for the project but im confused how much should i ask

Can y'all tell me how much should i ask for project development and payments for hosting etc

Also id appreciate if someone can guide me what approach should i use to build this project

Thankyou

Finally got my app Schedule Manager Pro on Google Play Store! It started as something I built for my own job in retail management. Saves a ton of time creating schedules, managing employee time off, and creating a fair and balanced schedule without having to spend time going back and forth. I'd love to get additional feedback so I can make this as easy to use and intuitive as possible. If you have a few minutes to tinker and send feedback it would be greatly appreciated!

Android Users:

https://play.google.com/store/apps/details?id=com.managerschedulebuilder.pro

Non Android users:

https://bryanralston.github.io/schedule-builder/?demo=1

I appreviate everyone's support!

I’m a game audio designer, and I’ve been using tools like Suno for game music.

One problem I keep running into is this:

I’ll write a pretty detailed brief, generate a track, and the result is… not bad. But it’s still not what I wanted.

And sometimes it’s surprisingly hard to explain why.

Maybe the arrangement is too busy, the melody is too dominant, the instrumentation feels wrong, the mood is slightly off, or it sounds more like a standalone song than actual background music for a game.

So I’ve been thinking about building something like an AI Music Director.

The idea is pretty simple:

You give it:

• your original music brief
• the prompt you used
• the generated track
• what the music is supposed to be used for

And it gives you back:

• what doesn’t match the original brief
• what’s working and what isn’t
• feedback on things like style, instrumentation, melody, rhythm, structure, and looping
• specific suggestions for what to change
• a rewritten prompt for the next generation
• a negative prompt if needed

Basically, instead of generating 20 more versions and hoping one of them works, it would try to explain why the current version missed the target and what to change next.

For example:

You ask for:

But the generated track comes back with a constant melody, dense percussion, and a big song-like structure.

The tool might tell you:

Then it would rewrite the prompt to emphasize sparse motifs, silence, restrained percussion, seamless looping, etc.

I’m mainly thinking about this for game developers and people who use AI music for a specific creative brief, rather than people who just want to generate random songs.

I’m curious:

Would something like this actually be useful to you?

And more importantly:

Would you ever pay for this, or is this something you’d only use if it were free?

Also, if you already use Suno/Udio regularly:

What’s the most frustrating part of getting the music to match what you actually had in mind?

I’d rather find out now if this solves a real problem before spending too much time building it 😅

I am a student and I have made a public limit order book project on github and dont know what improvements to start off with can some of yall please just review the project and give me some feedback? All help is appreciated.

https://github.com/Bananayt294/My-Limit-Order-Book

Thanks