Muhammad Zubair Alam

@Cuki98 Tysm will do

@ZubiTheDev leave it alone at least a week, ideally two. apple needs a learning phase and if you keep tweaking you reset it. and honestly time matters less than taps. don't touch a keyword till it has 20+ taps or you're just reacting to noise, not signal

unpopular opinion: running Apple ads for your iOS app is peak lazymaxxing -> no TikTok algorithm to crack -> no IG reels roulette -> no influencer negotiations just show up when someone searches for your app and it prints

@Cuki98 How long should I wait before modifying my advanced ad? Assuming the ad performs better over time?

@ZubiTheDev go advanced. basic has no keyword control so you can't chase cheap long tail, ends up 15-25% higher CPI. apple gives you $100 free credit for both when you start, so just test both and see

The amount of horrendous software making great money just through sheer grit and consistent sales is motivational.

@rehanxahmed If you don't lose much, become stern and simply refuse to do it unless paid explicitly

Hello Designers🥹 How do you guys deal with clients who are endlessly sending feedbacks?

@MarkKnd Congratulations

Just crossed $1M+ in revenue on Contra The first one on the platform

@BrettFromDJ I guess the one person business model is collapsing.

As a dad of 3 young daughters, I can already see how impactful this could be.

Wanted to go to ai4.io as my first conference for networking but it's costing me like $10k from Pakistan.

Mercury is amazing, but internet advice often forgets that the context of success really matters. Being able to pull off a fintech solution requires a certain environment, certain resources and the fact that products attached to money are often easy money makers. The only people with the luxury to work 5 days a week are those that often have some basics covered or taken care of. Immad is great. I wish my entire country wasn't restricted though.

100000% every single time I've tried to trust people and go against my inner feelings. I've been bitten.

Healthcare development isn't about technology preferences—it's about understanding how healthcare organizations actually work. What we've learned building 6 healthcare platforms: Compliance officers need audit logs they can query, not raw database dumps Regional managers need data scoped to their territory, not the whole org Frontline staff need mobile apps that work offline, not responsive web IT security needs architecture documentation that passes their questionnaire Executives need dashboards that show compliance status at a glance The technology stack matters less than whether your developers understand these personas and their workflows. We use React/Angular for web, Flutter for mobile, Node/Express for backends, MongoDB/PostgreSQL for data—but the stack is secondary to domain expertise. At Zee Palm, we combine healthcare domain knowledge with modern development. If you're evaluating agencies for a healthcare project, DM us to see how we approach your specific use case.

Feature flags in healthcare platforms aren't optional—they're how you handle gradual rollouts without breaking compliance. Our implementation: - Admin UI for toggling modules without deployment - Route-level guards that check flag status - Automatic redirects when disabled modules are accessed - Default-enabled pattern (missing flags default to on, only explicit false blocks) - A behavioral health client uses this to roll out new assessment types to specific locations before organization-wide release. The alternative—deploying new features to everyone simultaneously—creates compliance risk when you're still validating clinical workflows. At Zee Palm, we build healthcare platforms with operational controls that compliance teams appreciate. If you need controlled rollout capabilities, DM us.

Healthcare integrations we’ve implemented: Interoperability: HL7 v2 (ADT/ORM/ORU), FHIR (R4), NHIIS connectivity and reporting, CCD/C-CDA exports, custom EHR/EMR interfaces, and more Identity & Access: Enterprise SSO, Azure AD, Google OAuth, Apple Sign-In, custom JWT with role-based claims Payments: Stripe Connect with full webhook handling for clinical site payments Communications: Twilio for SMS, SendGrid for email, push notifications for mobile Infrastructure: Azure Key Vault for secrets, Azure Blob Storage for documents, MongoDB for data, Redis for caching and rate limiting Reporting & Compliance: DHHS result submissions, OSHA 300 log generation, PDF report generation with enterprise-grade libraries Each integration follows healthcare-specific patterns: audit logging on every external call, compliant error handling, idempotency, and retry logic for critical submissions. At Zee Palm, we integrate healthcare systems with the platforms your organization already uses. If you need custom integrations built by a team that understands healthcare, reach out.

The hidden cost of "cheap" healthcare development: A client came to us after spending 8 months with a generic SaaS dev shop. They had: - Basic CRUD operations - No multi-location support - Single-level user permissions - No audit logging - Manual credential tracking We rebuilt with: - 7-tier role hierarchy - Region and location scoping - Database-level access control - Comprehensive audit logging - Automated credential management with reminder schedules The rebuild took 1.5 months. They spent a year total instead of doing it right the first time. Healthcare software isn't hard because of the UI. it's hard because the business logic has regulatory requirements baked in and generic devs don't care. To many, your platform is not different for them if they were building an entertainment software. We've trained our team around the principles of healthcare and it shows. At Zee Palm, we build healthcare software correctly the first time. If you're starting a healthcare project and want to avoid expensive rebuilds, DM us.

Healthcare mobile apps have different requirements than consumer apps. What we've shipped: MedConnect - Doctor appointment booking with real-time chat, responsive design for tablet and desktop, admin panels for clinic management Physio On The Go - Physical therapy exercise library with video playback, custom workout builder, movement screening assessments, voice messaging, PDF report generation, real-time cloud sync Patient Talker - AI medical scribe for patients, The all-in-one health recorder app that helps you prepare thoroughly, capture every detail, and follow your care plan with confidence. Affili-Fit - A myfitnesspal alternative with special focus on corporate wellness, a suite of employee focused health and fitness platform supported on web and mobile. Both built with Flutter for native iOS/Android performance, HIPAA-eligible cloud infrastructure, and offline-capable data sync. We've also built Angular dashboards for healthcare analytics with Chart.js visualization and Material design—the kind of enterprise UI that healthcare admin teams expect. At Zee Palm, we build healthcare apps across mobile, web, and dashboard. If you need a development partner who understands clinical workflows, reach out.

Healthcare compliance platforms built by non-healthcare developers usually fail on the same things: ❌ Role hierarchies stop at "admin" and "user" ❌ Multi-location support requires separate instances ❌ Credential expiration tracking is manual ❌ Incident workflows end at "report submitted" ❌ Audit logs exist but aren't queryable We've built 6 healthcare platforms with proper role-based access (platform owner, platform staff, client admin, regional admin, local admin, manager, employee), multi-tenant architecture, automated credential tracking, full incident lifecycle management, and audit logs that compliance officers can actually use. The Simmons Safe platform handles 35+ feature modules across credentials, training, policies, incidents, forms, documents, and organizational hierarchy—all in one codebase. At Zee Palm, we build healthcare software that passes compliance audits. If you're evaluating development partners for a healthcare project, DM us.

Environment validation with Zod on healthcare frontends catches configuration errors at build time, not runtime. If someone deploys without setting required environment variables, the build fails. No more "it worked in dev" production incidents because someone forgot an environment variable. This is especially important in healthcare where a misconfigured project could mean patient data going to the wrong database. At Zee Palm, we implement fail-fast configuration validation on healthcare frontends. If your deployments have had env var incidents, DM me.

Healthcare API surface area gets large fast. One of our backends has 50+ route modules: - User management and auth - Organization and role administration - Patient records and lab results - Testing event scheduling and slot registration - Referral workflows (claims, requests, data, files, physicians, exams) - Online booking for clinical sites - Mobile booking for vaccination events - DHHS report submissions - Analytics dashboards - Stripe payments and webhooks Each module has its own authorization middleware chain. Some routes need organization admin access; others are open to authenticated users; payment routes skip auth entirely for webhooks. This is why healthcare backend architecture matters—you can't retrofit proper access control onto a monolithic API. At Zee Palm, we architect healthcare APIs for maintainability at scale. If your backend is becoming unmanageable, reach out.

Database security rules can enforce HIPAA access patterns at the query level—but most implementations stop at "user can read their own data." Our healthcare implementations include: - Platform owner vs platform staff permission differentiation - Client admin scoped to their organization - Location managers scoped to their assigned locations - Employees scoped to their own records within their org - Generic subcollection rules for extensibility The key pattern: belongsToOrg(orgId) and hasLocationAccess(locationId) helper functions that evaluate against JWT custom claims at the database layer. Even if someone bypasses the API and queries the database directly (which they shouldn't be able to), the security rules reject unauthorized reads. Defense in depth isn't optional in healthcare systems. At Zee Palm, we implement database-level access control for healthcare projects. If your security rules are wide open, we should talk.

Azure Key Vault integration changed how we handle secrets in healthcare backends. Environment files contain only the Key Vault connection info. Database credentials, API keys, encryption secrets—all pulled at startup from Azure. No secrets in source control. No secrets in deployment configs. Rotation happens in Key Vault without redeployment. For healthcare orgs with SOC 2 or HIPAA audits, this architecture satisfies "secrets management" requirements cleanly. At Zee Palm, we implement cloud-native secrets management for healthcare backends. If your secrets are still in .env files, let's fix that.