Mobile App Development

The admin panel: your app’s real control centre

The part of a mobile app you see is the tip of the iceberg. The real work happens in the web-based panel that lets you run the app day to day without a developer. The panel we ship with every app does the following:

Change content without a store update

Campaign banners, price lists, menus, announcement copy — change them in the panel and the app updates instantly. No store review to wait for. In apps where this separation isn’t built correctly from the start, a single price change means a 2–5 day App Store review; for seasonal businesses that is unacceptable.

User and content management

View registered users, suspend accounts, assign roles and permissions, moderate reviews and reports. In apps hosting user content, store approval itself gets harder without moderation tooling — Apple requires reporting and blocking mechanisms for user-generated content.

Sending push notifications

Send notifications to everyone or to a segment (city, last login, purchase history), schedule them, and read open-rate reports. Push is the single reason an app is worth more than your email list: open rates are multiples of email.

Analytics and reporting

Daily active users, per-screen usage, where users drop off, version distribution and crash reports. “Is the app doing well?” gets answered by a screen, not a hunch.

Working on every device

It isn’t enough for the app to “work” — it has to work on the device in the user’s hand. In Türkiye four-year-old Android phones are still in wide use, while iOS has broad screen-size variety. Our test coverage is built accordingly.

Phones, tablets and foldables

The interface is built on flexible layout rather than fixed pixels; the same app holds together from a 5-inch screen to a tablet. On foldables, state management is written so the app doesn’t restart when the screen opens or closes.

Older OS versions

Supporting only the newest iOS and Android means writing off a visible share of your audience from day one. We agree the target version range at project start; if you don’t know your audience’s device mix, we derive it from your existing site analytics.

Poor connectivity and offline mode

The field team is in a basement, the courier in a lift, the guest on hotel wifi. Making critical screens work offline — queueing entered data on the device and sending it when the connection returns — is separate engineering work that is hard to bolt on later.

Accessibility and system settings

If the user has enlarged text on their phone, the app should follow; if dark mode is on, the app should be dark too. These aren’t details — an app whose layout breaks at larger text sizes loses exactly the users who need it most.

How an app makes money

An app can stay a cost line, or become an asset that pays for itself. The difference is whether the revenue model was designed in from the start or added later. We build the models below individually or in combination.

Subscriptions (the most predictable revenue)

Monthly or annual subscriptions are the steadiest app revenue: you don’t have to make the sale again each month. With a free trial, an annual discount and a well-built cancellation flow, churn drops noticeably. Apple and Google take a commission on subscriptions; the rate falls after the first year, so the model improves over time.

In-app purchases

One-off feature unlocks, credit or token packs, premium content, or an ad-free version. If you sell digital content you must use the stores’ payment systems. If you sell physical goods or services you can use your own payment infrastructure — apps that get this distinction wrong are rejected by the stores.

Ad revenue

In apps with a large, regularly-used audience, ad networks (such as AdMob) generate passive income. Banners, interstitials and rewarded video carry different revenue-versus-annoyance trade-offs: rewarded video draws the fewest complaints and earns the most, because the user opts in. Note: ad revenue scales linearly with users, so it isn’t a meaningful line for small audiences — subscriptions fit better there.

Escaping commissions (indirect revenue)

If you run a restaurant, salon or hotel, the app’s biggest return isn’t new revenue but the commission you stop paying. Where platform orders carry 15–30% commission, orders through your own app carry none. In this model the app can cover its own cost within a few months.

Loyalty and repeat sales

Points, personalised offers and “every tenth coffee free” work far better in an app than on a website, because the user is already signed in and reachable by notification. Selling again to an existing customer is far cheaper than acquiring a new one.

After release: shipping isn’t the finish line

Store updates are mandatory

Apple and Google release a new OS every year and require apps built with older SDKs to be updated. An app left untouched for years eventually gets removed from the store. A maintenance plan isn’t an upsell — it’s the app’s survival condition.

Store accounts are opened in your name

Apple Developer and Google Play accounts are opened under your company; you own the app. An app sitting in an agency’s account becomes hostage the day you part ways — the most common and latest-noticed problem in this industry.

Store visibility (ASO)

App name, subtitle, keyword field, screenshots and preview video determine your rank in store search. Getting these right at launch beats fixing them later, because store algorithms weight download momentum in the first weeks.