Ingenii / Mobile game publishing

Get your mobile game
ready for publishers.

Start with a free playable-build review. Get practical feedback, optional paid preparation and help approaching suitable publishers.

How we help

A clear next step
for your game.

01 · Free initial review

Show us your game.

A short written assessment of the game loop, first session and readiness for publisher conversations, with a clear next step.

02 · Paid preparation

Get ready to pitch.

An agreed scope: game improvements, a pitch deck, gameplay footage and a funding or development brief. Deliverables and price are agreed first.

03 · Separate deal fee

Speak to suitable publishers.

A reasoned shortlist, approved introductions, follow-ups and offer coordination. Representation terms and any deal fee are agreed before outreach.

Already ready to pitch? You can skip preparation. Any deal fee and when it becomes payable are agreed in writing before outreach.

Nikhil Pote
Your review contact

Nikhil Pote · Ingenii

Nikhil coordinates the review and your next steps. Our development work includes mobile multiplayer games and interactive 3D.

See the work behind our technical perspective ↗
See an example assessment and publisher shortlist

Illustrative example only: the game below is invented. It is not a client result, an actual review or a publisher commitment.

Example: a playable mobile puzzle game

What works
A clear goal and a short, repeatable puzzle loop.
What needs work
The first puzzle needs a clearer hint. Difficulty progression needs playtesting.
Readiness
Prepare a short gameplay video, team plan and development budget. Label any missing player data.
Next step
Improve onboarding, then check suitable publishers’ current requirements.

How we explain a potential match

  • Voodoo: research its casual publishing focus and current testing requirements against this game’s loop and business model.
  • Kwalee: compare the game with its current mobile publishing brief, stage requirements and submission route.

These are research starting points, not existing Ingenii partnerships or confirmed interest. A real shortlist depends on the game, current publisher requirements and developer approval.

What happens after you send a game?
  1. We check access to your testing link and email you if anything is missing.
  2. We try the game and assess its core loop, first session and technical readiness.
  3. You receive a written next step: prepare something specific, discuss representation, or an explanation of why we cannot help yet.

Paid preparation is optional. If we recommend development work, we explain why and quote it separately.

Send your game

Request a game review.

Any mobile genre is welcome. Send a playable Android or iPhone build; an early version is fine.

What you’ll need

  • Your name and contact email
  • A TestFlight or Google Play testing link
  • The game name and a short explanation of how to play

No pitch deck or file upload is needed for the initial review.

First, read and accept our confidentiality agreement. Then share your game. Publisher sharing needs separate permission.

Read how we protect your game ↗
Step 1 · Confidentiality

Agree before you share.

Ingenii will keep your unpublished game materials confidential and use them for review. You keep ownership.

Read the full confidentiality agreement

Version game-review-nda-2026-11-05

Parties: Ingenii Digitalization LLP (Ingenii), represented by Nikhil Pote, and the individual or legal entity identified by the developer in the acceptance record (Developer). A person acting for a studio must have authority to agree for that legal entity. Purpose: Allow Ingenii to privately assess the Developer's mobile game and related publishing needs, and discuss possible advice or representation. 1. Confidential information Non-public game details, descriptions, testing links, builds accessed through those links, gameplay footage, designs, pitches, business plans, budgets and performance information disclosed to Ingenii for this purpose. Information need not be labelled confidential if its nature or the circumstances make that clear. Material already public remains public; sharing a public store link does not make the public store listing confidential. 2. Ingenii's commitments Use the information only for the stated purpose. Do not publish, sell, license, or use it to build or help another party build a competing game. Limit access to personnel and professional advisers who need it for the review and are bound by confidentiality duties. Ingenii remains responsible for its personnel's compliance with these commitments. Use reasonable security measures, and notify the Developer without undue delay if Ingenii becomes aware of unauthorised access to or disclosure of their confidential information. 3. Publisher sharing needs separate permission This agreement does not authorise Ingenii to send the game or materials to publishers. Agree the recipients and materials with the Developer separately, and explain the confidentiality terms under which each publisher will receive information. This agreement does not itself bind a publisher or Apple/Google. 4. Developer ownership The Developer keeps ownership of the game and materials. Ingenii receives only the limited permission needed to access and review what the Developer shares. No assignment of IP, portfolio permission, publishing licence, exclusivity, representation authority, development work or payment obligation is created. Do not send source code, account passwords or material you cannot lawfully share. 5. Exceptions The duties do not cover information Ingenii can demonstrate was already lawfully known, becomes public without breach, is independently developed without use of the confidential information, or is lawfully received from a third party without a duty of confidence. Similar ideas alone do not establish misuse; the obligation not to use confidential material still applies. 6. Required disclosure If the law requires disclosure, disclose only what is required and, where legally permitted, notify the Developer beforehand so they can seek protection. 7. Duration For information disclosed for this review and related follow-up, confidentiality and restricted-use duties continue for three years after each disclosure. Information that qualifies as a trade secret remains protected while it remains a trade secret under applicable law. Ending discussions does not end these duties. 8. Return, deletion and records On written request, stop the review and delete confidential materials from active systems within 30 days, except records reasonably needed for legal or compliance purposes. Backups may remain until their normal rotation and must not be used for another purpose. Any retained confidential material remains protected. Review submissions normally expire after 180 days. Agreement and acceptance records are retained for five years as evidence of the terms agreed; this does not give permission to keep using the game materials. 9. Electronic acceptance Ingenii makes these terms available as its offer of confidentiality for game review. Acceptance takes effect when the Developer expressly agrees and the website successfully records acceptance, before the game submission step opens. The receipt identifies the parties, exact version, text hash and server-recorded acceptance time. A typed name and checkbox record electronic acceptance; they are not a certified digital signature, an independently verified identity, or an officer's handwritten countersignature. A formal signing service can be used instead if agreed. 10. Other terms This confidentiality agreement takes priority over conflicting general website terms for covered game-review disclosures, including portfolio permissions and fee-based liability limits. Indian law applies, subject to any mandatory rights that cannot be excluded. Parties may seek remedies available under applicable law. Changes require express agreement; updating the website does not change an existing acceptance. No publishing deal or review outcome is guaranteed. Contact: business@ingeniidigital.com
Leave blank if you are agreeing as an individual.

This records online acceptance, not a certified digital signature. No game details are sent in this step.

Need a separately signed NDA? Contact us before sharing confidential details.

A playable game, one simple link

Where do I get my testing link?

Create a testing link in your platform’s developer console, then paste it into the form. Your game stays on Apple or Google’s testing service.

iPhone / iPad — TestFlight
  1. In App Store Connect, choose your game and open TestFlight.
  2. If this is your first setup, create an internal group first. Under External Testing, select or create an external group and add a build. The first external build needs Apple’s beta review approval.
  3. Open the group’s Testers tab and choose Create Public Link. Set access to Open to Anyone or choose compatible device criteria.
  4. Confirm, copy the link, and paste it here. It looks like https://testflight.apple.com/join/AbCd1234.

Keep the link enabled, leave a tester slot available, and check that the build has not expired. An internal-only TestFlight build cannot be shared with us through a public link.

Apple’s TestFlight instructions
Android — Google Play open or closed testing
  1. In Play Console, select your game and open Test and release → Testing.
  2. Choose Open testing or your Closed testing track. Roll out a test release, then open its Testers tab.
  3. Copy the shareable testing / opt-in link and paste it here. It usually starts with https://play.google.com/apps/testing/.

A closed-test link works only for eligible testers. If you use a Google Group, let us know how to join when we reply. A link alone does not bypass an email allowlist. For easy access, use open testing if available.

Google’s testing instructions
Android — internal testing or internal app sharing

For an internal test track, roll out a release, open the Testers tab, and copy the shareable link. Access is restricted to eligible testers; we’ll coordinate access by email if needed.

For Internal app sharing, generate the share link in Play Console and, if appropriate, allow anyone with the link to download. Paste that Google Play link here. You do not upload a build to Ingenii.

Google’s internal app sharing guide

Instructions checked 3 Nov 2026. Console wording may vary. Never share developer-account credentials or console admin links.

A few things to know

Before you hit send.

Do I need a finished game or a pitch deck?

An early working version is enough. Send a testing link and explain how to play.

What happens after I submit?

We check access, try the game and email a short assessment with a next step. We may suggest preparation, discuss representation or explain why we cannot help yet. Any paid work needs your agreement first.

Is my game confidential?

Read and accept our confidentiality agreement before sharing a game. We record your acceptance and provide a downloadable receipt. You keep ownership. We ask separately before sharing with publishers; this agreement does not bind a publisher. If you need formal signatures, contact us before sharing confidential details.

What does it cost?

The initial review is free. Game and pitch preparation is paid work, quoted before starting. Publisher representation has a separate deal fee, with the amount and payment conditions agreed in writing before outreach. Submitting your game does not commit you to either service.

Will you send my game to every publisher?

No. We choose suitable publishers and ask for your permission before contacting them.

Does a review guarantee a publishing deal?

No. Each publisher decides which games to support. We help you prepare and talk to them.