App Publishing
We take an app from finished build to live listing on Google Play and the App Store — including the parts people underestimate, like signing keys, data-safety declarations and the review back-and-forth that decides whether a release ships this week or next month.
What publishing actually involves
Android & iOS builds
Native builds, or a web app wrapped with Capacitor where that is the sensible call — the choice follows the product, not habit.
Signing & keystores
Upload and signing keys generated, documented and backed up. Lose these and you cannot update your own app; they stay with you.
Store listings
Title, description, feature graphic, screenshots and categories written and sized to each store’s spec rather than resized guesswork.
Policy & compliance
Privacy policy, data-safety declarations, content ratings and permissions justified — the paperwork that quietly fails most first submissions.
Submission & review
Release tracks, staged rollout, and handling the review back-and-forth so a rejection costs days rather than weeks.
Updates after launch
Version bumps, release notes and staged updates, so shipping a fix is routine instead of an event.
Already have a website?
A web app can often be wrapped and published without rebuilding it from scratch — that is how the Khpal Dukan apps below were shipped. One codebase, one set of updates, and a presence on the stores. We will tell you honestly whether that fits your product or whether a native build is the better answer.
Khpal Dukan — KPK Marketplace Apps
Buyer and seller Android apps for a Khyber Pakhtunkhwa marketplace — Capacitor builds over the live portals, signed and packaged for Play Store release.
Khpal Dukan — KPK Marketplace Apps
Khpal Dukan is an online marketplace for Khyber Pakhtunkhwa, Pakistan — local shops, local riders, cash on delivery. We built the Android apps: one for shoppers, one for the sellers supplying them.
Capacitor over the live platform
Both apps are Capacitor builds wrapping the live buyer and seller portals.
The alternative — separate native Android and iOS codebases alongside the web platform — means writing the same feature three times and keeping three release cycles in step. For a marketplace still iterating on its catalogue, checkout and seller tools, that is the wrong trade. With Capacitor a change ships to web and mobile at once, and the team maintains one codebase instead of three.
What Capacitor does not give you for free is an app that feels native. That part is configuration, and it was done rather than left at defaults:
- Splash screen and status bar themed to the brand instead of the framework’s white default.
- HTTPS-only with mixed content blocked, so the webview cannot silently load insecure resources.
- Standalone display mode, so the app never reads as a browser with the address bar hidden.
The seller app
com.khpaldukan.seller — product and inventory management, order tracking, sales analytics, promotions and payouts. This is the side of a marketplace that decides whether it survives: sellers who cannot manage stock or see their money stop listing, and a marketplace with no sellers has nothing to show buyers.
The buyer app
Browse by category, flash deals, cash on delivery and order tracking.
Cash on delivery is the important one. Card penetration in this market is low and trust in online payment is lower still, so a checkout that assumes a card excludes most of the customer base before it starts. The platform is also location-first: before showing anything it asks for the shopper’s location and resolves it to the nearest city, so what appears is shops that can actually deliver to them rather than a national catalogue they cannot order from.
Release
Signed release bundles (.aab) generated and prepared for Play Store distribution for both apps, with the upload key backed up — the one genuinely irreversible mistake in Android publishing, since losing it means never being able to update the listing again.
Stack: Capacitor over the live web platform, Android release bundles, Play Store packaging.
ePlay — Master League
Android build of a competitive football league platform — season standings, six game modes and a social layer, packaged and signed for Play Store release.
ePlay — Master League
ePlay — Master League is a platform for organised online football leagues running across mobile, console and PC. We built and packaged the Android release.
What it replaces
Competitive gaming communities of this kind almost always run on a spreadsheet. Someone volunteers to maintain it, fixtures get posted in a group chat, results are reported by message, and the table stays accurate until that person loses interest.
ePlay makes the season the software’s job. A standard season is 20 players, double round-robin, 38 matches each, with standings, fixtures and results tracked automatically.
Six competition modes
- FIFA World Cup 2026 — an authentic 48-team format, run in three variants (Authentic, Immersion and Dream Team) competing for a single trophy.
- eFootball Mobile Online Master League.
- eFootball Console Online Master League — PS5 and Steam.
- UFL Mobile Quick Play — four-player rooms, create or join.
- Build Your Own League — private and invite-only.
- Classics — retro PES and FIFA, PES 13–21 played over Parsec, PC only.
The social layer is the retention mechanism
A league table on its own does not hold a community together between seasons. Player profiles carry reliability ratings, club badges and W-D-L records, with following and in-app messaging.
The reliability rating is the load-bearing feature. The thing that kills an amateur online league is players who do not turn up for fixtures; making reliability visible and persistent lets the community police that itself, instead of leaving an organiser to chase people privately until they give up.
One hub, six seasons
With six modes running at once, the navigation problem is real: a player cares about the one league they are in, not the five they are not. The platform is organised as a hub — Dashboard, Standings, Leagues, World Cup, Classics and Social — so a player lands on their own season rather than a menu of everything on offer, while the modes they are not playing stay one tap away rather than hidden.
The interface also ships bilingual, with an Arabic toggle alongside English, reflecting where a large share of the competitive eFootball community actually plays. That is a layout consideration as much as a translation one, since switching to Arabic flips the reading direction of the whole interface.
Android packaging
- Package
com.eplay.masterleague, version 1.0.0. - Standalone display mode, so it runs as an app rather than a browser tab.
- Dark theme carried through splash, status bar and navigation bar — left at defaults the system chrome flashes white on launch and breaks the illusion immediately.
- Signed release bundle generated and prepared for Play Store release.
Stack: Android packaging over the ePlay web platform, signed .aab for Play Store distribution.