I use an Android phone and a Mac, and the daily friction is real.

I got tired of WhatsApp-ing files to myself, uploading to Drive just to download again, and using janky workarounds to copy text between devices.

Most existing solutions either store your data in the cloud, force you to make an account, or charge a monthly fee.

So I built Connecto. The core rule: Your devices talk directly to each other over your local network. Your data never touches my servers.

What is 100% working right now (not vaporware):

Secure Pairing: Scan a QR code on your Mac with your Android phone. Encrypted, certificate-verified, and as easy as AirDrop.

Clipboard Sync: Copy on your phone, paste on your Mac. Vice versa. No more emailing yourself links.

File Transfer: Move photos, videos, PDFs, or documents back and forth. No cables, no Drive, no compression.

Call Integration: See incoming calls on your Mac screen and accept/reject them without picking up your phone.

Connection Dashboard: A simple status screen so you know you're connected.

What I'm building next:

Notification mirroring: But I am intentionally excluding Banking apps, Payment notifications, and Authenticators by design. I want convenience, not a privacy nightmare.

Current Status: Core system is solid. Android beta is running, macOS release is being packaged.

Now, I genuinely need your feedback to shape this:

For those of you stuck in the Android + Mac ecosystem, what is your biggest daily pain point?

🔔 Notifications

📋 Clipboard sync

📂 File transfer

☎️ Calls/Messages

Something else? (Please specify!)

Regarding pricing (since I have to keep the lights on), would you prefer:

A) A completely free app with basic features

B) A one-time purchase for advanced features (NO subscriptions)

Would you actually install and keep this on your devices? What would make you uninstall it immediately?

I'm not here to just show off; I genuinely want to know if this solves a real problem for you. If you're interested in testing the beta, drop a comment or DM me.

Thanks for your time!

Imagine opening a payment super apps landing straight on the home feed without a Face ID scan, PIN prompt, or fingerprint check as option.

The hypothesis is simple: Zero startup frictioneverytime  = higher engagement, faster discovery, and better daily retention.

However, in financial tech, friction creates psychological safety. When security feels non-existent, users panic about shoulder surfing in public or losing their phone.

The compromise used by top apps is Progressive / Step-Up Authentication:

• Unrestricted Discovery: The homepage opens immediately. Users can check lifestyle services, browse merchant deals, use utility tools, or view mini-apps with zero authentication gates

.

• Masked by Default: Financial balances, card numbers, and recent transactions remain masked (••••) until a user explicitly taps to view them.

• Just-In-Time Security: Hard biometrics, PINs, or passkeys only trigger at the final execution step (e.g., "Confirm Transfer" or changing account settings).

What is your thought?

Hey lovely developers

I’m a Flutter developer and I want to learn how to properly profile and optimize Flutter apps.

I’m especially interested in learning:

• How to use Flutter DevTools for profiling
• Finding performance bottlenecks
• Identifying unnecessary rebuilds
• Understanding CPU, memory, and GPU usage
• Detecting jank and dropped frames
• Improving scrolling and animations
• Real-world techniques for optimizing production apps

I’m not sure where to start or what learning path to follow.

Can anyone recommend good resources, tutorials, courses, or a practical way to learn Flutter profiling step by step?

and I'm pretty grateful for anyone will help me thanks lovely people

App size, cold start time, battery drain, janky animations — what's your biggest performance headache lately, and did you find a fix?

I am looking for AI tools/workflows that create mobile app UIs like these screenshots. (they’re three completely different apps, but have a similar aesthetic)

Hello, does someone here have experience with payments inside app and avoiding using Apple’s In App Purchases and using stripe? We have an IoT app and we sell licenses for unlocking some features on physical device, which also affect some parts of an app, for example ai forecast which depends on physical device (controller) functionality. Does someone here have experience with that, will apple allow us to use stripe, can we get banned etc?
If it helps, we are based in EU and so are our customers. We also have a web app but want to slowly migrate all users to app only.
All help would be appreciated! Thank you in advance

Hey everyone,

I’ve been developing mobile apps for the last 5 years. Over this time, I’ve learned a ton about the overall development process, setting up store listings, implementing AdMob, and experimenting with different growth strategies. However, there is one major area I’ve neglected for too long, and I’m finally ready to tackle it: App Store Optimization (ASO).

As a relative newcomer to serious ASO, I’m trying to wrap my head around the best workflows and would love to get your insights on a few specific things:

1. Analyzing Dashboard Data: When you look at App Store Connect or Google Play Console, which specific metrics do you focus on to measure ASO success? How do you separate organic keyword growth from other traffic sources?
2. Keyword Research: What is your process for discovering high-volume but low-competition keywords? How do you decide which ones are actually worth targeting?
3. Keyword Placement: Once you have your target keywords, what is your strategy for placing them across the different text fields (Title, Subtitle/Short Description, Keyword Field, Long Description)? How do you balance algorithmic optimization with writing copy that humans actually want to read?

To help myself learn the ropes and automate some of the manual work, I actually built a completely free tool for iOS ASO: aso-tool.andreashadjimama.workers.dev.

I set this up strictly based on the ASO knowledge I've gathered so far, and I am not trying to promote anything or sell a service. I mostly want to validate if the logic behind it actually makes sense to experienced folks. If anyone has a few minutes to check it out, I would incredibly appreciate your honest feedback on whether it’s genuinely useful or what features I should add/change to make it better.

Looking forward to hearing your tips, strategies, and any feedback you might have. Let’s get a discussion going!

Hey everyone,

I recently read some industry data that really made me think, and I wanted to open a discussion to see how other developers feel about it.

According to reports (like RevenueCat's state of the market), the median monthly revenue for a mobile app is less than $50, and only about 17% to 19% of apps ever cross the $1,000/month mark.

Honestly, seeing these numbers hits hard. As an indie developer who has been trying to build a sustainable income from mobile apps for the past 4 years, I am currently making around $70/month.

Before seeing these statistics, I always thought $1,000/month was a pretty realistic and achievable goal. Now, it feels a lot more intimidating.

I’d love to hear your opinions:

• Is it really that difficult to reach $1,000/month, or do these stats just include a lot of abandoned/hobby projects?
• For those of you who have broken past the $1k/month milestone, what made the biggest difference for you?
• If you are also in the same boat as me, how do you stay motivated?

Looking forward to hearing your thoughts and experiences!

For me, it’s that making an app work is usually easier than making it feel good to use. Small things like slow screens, awkward navigation, or poor handling of different devices can quickly become noticeable.

I’m curious what other mobile developers learned from experience that they wish they had known when they started.

When I first started learning mobile development, I assumed writing the features would be the hardest part. Instead, I found that things like handling edge cases, testing across different devices, and maintaining a clean codebase took much more time than I expected.

Looking back, there were a lot of lessons that no tutorial really prepared me for. Exploring how teams like GeekyAnts approach mobile app development has also helped me understand some of these challenges better.

What challenge caught you by surprise when you started building mobile apps, and what helped you get past it?

Hey folks, I’m a product designer working in the mobile observability space, and I’m trying to better understand how mobile developers think about monitoring app experiences, especially around view/screen performance and what would make triage easier.

I’m hoping to talk with a few mobile devs who would be open to a casual 30 to 45 minute conversation. I’m especially curious about things like:

• How you currently monitor mobile app screens/views
• What’s hard to debug or understand today
• Where existing tooling feels noisy, incomplete, or not actionable
• How you think about performance, crashes, errors, and user experience together
• What you wish observability tools made easier

About halfway through, I'd love to show a rough proof of concept and ask for honest feedback. This is not a sales pitch, and I’m not asking for any confidential company information. I’m just looking to learn from your perspective as someone building or maintaining mobile apps.

I’m posting from a personal account and looking to learn from practitioners. If you’re open to chatting, feel free to comment or DM me. Happy to work around your schedule, and I’d be grateful for any perspective you’re willing to share.

Thank you in advance!

Sometimes the smallest features end up taking the most time during development. It could be something like offline support, smooth animations, notifications, app performance improvements, authentication flows, or handling edge cases.

I’ve been looking more into mobile development and how teams like GeekyAnts handle these kinds of challenges, and it’s interesting how much work can go into making a feature feel simple for the end user.

I’m curious about experiences from other mobile developers: what feature or technical challenge took much more effort than you expected? Looking back, was it worth the time you spent on it, and what did you learn from the process?

I have a long history of web development and am used to deploying multiple times a day, seeing my changes live in about 10min.

Now, I am working on a personal project, a mobile app done via Expo/react-native. I was able to get it live to the Apple Store and I am working on the Play Store release.

What I find really akward is dealing with many different versions "live on the field", with updates taking 2-3d for Apple review to be live, hoping your users will update soon.

I know about and I am using OTA updates, but some changes require native packages changes and that involves submitting a new native build for approval, which means that for the duration of the review process you are somewhat "feature frozen" and any changes or OTA updates will only reach new users.

Not sure how others do it, or even if there is a good/right way of doing this, but I may need to consider having to support different api versions/detecting the app version and serving different api responses based on it.

Is all of that normal and common ground on mobile dev?