Services
App Store & Google Play publishing
Store releases are part of the job — not a handoff at the end. I've shipped Framework7 + Cordova apps to both stores since 2020 on live delivery and marketplace platforms.
What publishing actually includes
Signing, bundle IDs, store listings, screenshots, privacy labels, review notes, and the back-and-forth when Apple or Google asks questions. For Cordova apps that means iOS certificates, provisioning profiles, Android keystore discipline, and build configs that do not drift between releases.
I treat publishing as ongoing — first submission, feature updates, OS compatibility bumps, and hotfixes when a store policy changes mid-quarter.
Framework7 + Cordova in production
Most of my store history is hybrid — one codebase, both platforms, PHP backend behind it. That stack is still practical for delivery, booking, and multi-role marketplace apps when the team is small and the backend is already PHP.
If you have an existing Cordova app that needs store maintenance, send the repo state and current store links. I can pick up releases without rewriting the product on day one.
Review prep and common rejections
Privacy policy URLs, permission strings, login/demo accounts for reviewers, and accurate metadata — I build these into the release checklist, not as an afterthought.
Common fixes: location permission copy that matches actual use, payment flows that follow store rules, and making sure the app does not look broken on a clean install with no backend seed data.
How this fits mobile development
Publishing sits inside full mobile delivery — process flows, PHP APIs, admin tools, and consumer apps that stay in sync. See mobile app development and Framework7 & Cordova service pages for the full picture.
React Native releases follow the same discipline when projects call for it — I am building that path on real work; Cordova remains my production depth for live platforms.
FAQ
Questions I get asked
Do you only publish, or build the app too?
Both. Publishing-only is fine for existing Cordova apps with a clear codebase. Most clients hire me for the full loop — mobile, backend, admin, and store releases.
How long does a first App Store submission take?
Depends on app complexity and account setup. A prepared Cordova app with listings and review assets ready can move in days; first-time developer accounts, missing privacy docs, or backend dependencies add time. I'll give you a straight timeline after seeing scope.
Can you fix a rejected app?
Yes — rejection notes, metadata fixes, permission copy, broken reviewer login, and build issues are normal maintenance work for me.
iOS and Android from one Cordova codebase?
Usually yes. Platform-specific store rules and device testing still get their own pass before each release.
What's your main stack?
Day to day it's Framework7, Cordova, PHP, and MySQL — mobile, backend, and getting apps through Google Play and the App Store. I'm building React, React Native, and Next.js through actual projects (this portfolio included). I'll pick up new tools when there's a clear workflow and time to review before release.
How do you use AI without breaking production?
AI helps me draft UI, boilerplate, and scaffolding. It doesn't get the final say. I still walk through security, logic, integrations, and store requirements myself — same as I have for years of releases on live platforms. Fast drafts, careful ship.
Do you work with teams outside the Philippines?
Yes. I'm based in the Philippines and work with local teams and remote clients. English is fine, and I'm used to coordinating across time zones on production teams and direct collaboration.
Related