Android TV Apps and Google Play Testing Tracks

Android TV apps run on a very different form factor from traditional phone and tablet applications. Users interact with a large living-room screen, usually through a remote or directional controller rather than touch, and Android TV apps have their own usability, navigation, layout, and quality requirements. For eligible new personal developer accounts, Google Play may require a closed test with at least 12 testers opted in continuously for 14 days before the developer can apply for production access.

The Google Play testing-track workflow is broadly similar across Android device categories, but the actual testing experience can be very different. Android TV introduces remote-based navigation, D-pad focus, the ten-foot user interface, large-screen layouts, and TV-specific quality expectations. Testing on real TV hardware is therefore particularly valuable because many problems cannot be discovered through ordinary phone testing.

If your application supports both phones/tablets and Android TV, make sure your testing strategy covers the device types you intend to support. If your application is Android TV-only, your tester recruitment must specifically target compatible TV devices.

The requirement for Android TV apps

Google Play's production-access requirements depend on the developer account type and the eligibility rules shown in Play Console. For eligible new personal developer accounts, a developer may need to complete a closed test with at least 12 testers opted in continuously for 14 days before applying for production access. Android TV apps are not automatically exempt simply because they target a different form factor.

The exact eligibility status should always be checked inside your own Play Console because Google can apply different requirements depending on account type, account history, app status, and current Play policies. See the Google Play closed testing guide and the official Android TV documentation.

Google Play provides testing tracks such as internal and closed testing, with the appropriate track depending on your development and release stage. If your account requires a closed test before production access, the closed-testing track is the relevant track for that requirement.

For Android TV, however, meeting the numerical tester requirement is only part of the testing strategy. The quality of the tester group also matters because TV-specific behavior can only be properly evaluated when testers can use a compatible TV device and interact with the application using the intended remote or controller.

Testing the ten-foot UI

The defining characteristic of TV applications is the ten-foot user interface. Users typically sit several feet away from a large display, so an interface that looks acceptable on a phone, tablet, or desktop monitor can become difficult to use on a television.

Text needs to remain readable from a normal viewing distance, interactive elements need to be appropriately sized, layouts should take advantage of the large landscape display, and important interactions must work without relying on touchscreen gestures.

Focus handling is particularly important. When a user moves through an application using a remote, there must always be a clear visual indication of which element currently has focus. Poor focus behavior can make an otherwise functional application frustrating or unusable.

See UI testing before publishing for broader guidance on preparing an Android application for release.

Remote navigation and focus

Unlike a phone application, an Android TV application cannot assume that the user can simply tap an element. Navigation should work naturally with directional controls, remote buttons, and other supported TV input methods.

During testing, move through every important screen using only the remote. Check that focus moves logically between elements, that no important control becomes unreachable, and that the back button behaves consistently.

Pay particular attention to situations where focus can become trapped inside a menu, disappear after a screen transition, jump unexpectedly to another part of the interface, or land on an element that is not visually obvious.

Testing with an actual remote or a device that accurately emulates TV remote input is preferable to assuming that mouse-based desktop testing represents the real experience.

A developer can often move a mouse directly to any button during development. A TV user cannot. The tester must reach that same button through the application's focus system. This difference makes real remote-based testing essential for discovering dead ends, unexpected focus jumps, and unreachable controls.

Review Google's TV app quality guidelines when validating navigation and user experience.

Meeting TV app quality guidelines

Android TV applications have platform-specific quality expectations covering areas such as navigation, visual design, input handling, media playback, and overall usability. Developers should review these requirements before submitting an application for production rather than waiting until the final review stage.

During testing, pay particular attention to:

• Correct directional navigation.
• Clear and consistent focus indicators.
• Layouts designed for large screens.
• Readable text at a normal viewing distance.
• Controls that do not depend on touchscreen interaction.
• Content that remains within appropriate screen-safe areas.
• Reliable back-button behavior.
• Accessible and predictable media controls when applicable.
• Stable performance on the TV devices you intend to support.

Testing on actual Android TV or Google TV hardware provides additional confidence because it validates the application in the environment in which users will actually experience it.

The closed-testing period can therefore serve two purposes: satisfying any applicable Google Play testing requirement and identifying TV-specific usability or stability problems before production.

Finding Android TV testers

Recruiting testers for an Android TV-only application is different from recruiting ordinary Android phone testers. A person who can test an Android application on a phone does not necessarily have a compatible Android TV or Google TV device.

For meaningful TV coverage, prioritize testers who can actually install the application on compatible TV hardware. Ideally, your tester group should represent the devices and environments your target audience is likely to use.

You can recruit Android TV testers through your own network, existing customers, Android TV communities, developer communities, social groups, beta-testing communities, or a testing service that explicitly confirms that it provides compatible TV devices.

When choosing a TV testing service, ask specifically about device coverage. Do not assume that a service offering "Android testers" automatically provides Android TV testers. Confirm the supported form factors before purchasing.

If your application supports Android phones or tablets and you need closed-testing testers for those supported devices, you can learn more about FastTesters. For an Android TV-only application, use a TV-specific tester recruitment method instead.

Setting up your Android TV closed-testing track

Once your signed release AAB is ready, create the appropriate testing track in Google Play Console and upload the bundle. Testers can typically be managed through email lists or Google Groups, depending on your chosen configuration.

For a closed test, testers need to complete the appropriate opt-in process before installing the test version. Make sure the track is properly configured and available before sending invitations to your tester group.

See how to create a closed-testing track in Play Console for the general setup process.

For an Android TV-only application, perform an additional device-specific verification before recruiting your full tester group. Confirm that the application can be installed and launched on at least one compatible Android TV or Google TV device from the intended Google Play distribution flow.

Do not assume that successful installation on an Android phone means that the TV experience is correctly configured. Android TV applications can have different device-compatibility requirements and different interaction models.

Where possible, test the opt-in and installation process yourself on the same type of TV hardware your testers will use. This can reveal compatibility, distribution, or configuration problems before the official testing period becomes important.

Provide testers with simple onboarding instructions covering:

• Which Google account should be used.
• How to join the closed test.
• How to install the application on the TV.
• How to update the application when a new build is released.
• Which remote controls and features they should test.
• How to report crashes, navigation problems, or other issues.

Clear onboarding is especially important when working with non-technical TV testers. A tester who receives an invitation but never completes the opt-in or installation process may not contribute to the testing requirement in the way you expect.

Managing the 14-day window

If your Play Console account requires the 14-day closed-testing period, plan for the full continuous window rather than treating the requirement as simply reaching a tester count once.

For eligible new personal developer accounts, Google currently describes the requirement as at least 12 testers opted in continuously for 14 days before the developer can apply for production access. Always verify the exact status and eligibility information displayed in your own Play Console.

For Android TV applications, maintaining a buffer above the minimum can be especially useful because TV-capable testers are generally harder to recruit than ordinary phone testers. If one tester becomes unavailable or encounters a device problem, having additional testers can reduce the risk of falling below your target.

During the testing period, give testers practical tasks that reflect real TV usage. Ask them to:

• Navigate the complete application using the remote.
• Move through menus and settings.
• Open and close dialogs.
• Test the back button.
• Move focus between different sections.
• Play and pause media if applicable.
• Test login and account flows.
• Check loading states and error messages.
• Use the application for realistic viewing sessions.
• Report crashes, freezes, or navigation problems.

Monitor your testing status in Play Console throughout the window. If your tester count or testing activity falls below what Google requires, investigate the issue immediately rather than waiting until the end of the 14 days.

For TV applications, also monitor device-specific problems. A tester may technically install the application while still experiencing serious problems with remote navigation, focus, playback, performance, or screen layout.

See how to keep testers engaged during closed testing for additional guidance on maintaining tester participation.

Can FastTesters test Android TV apps?

Important: Google Play supports testing for Android TV applications, but FastTesters currently provides closed-testing support for Android phone and tablet applications. We do not currently provide a dedicated Android TV tester network or physical TV-device testing service.

This distinction is important because an app can appear normally inside a Google Play closed-testing track while still being unavailable to the Android phones and tablets used by FastTesters testers.

If your application is designed exclusively for Android TV, you should not submit it to FastTesters expecting TV-device testing. Our testers are recruited primarily for Android phone and tablet applications, and they may not have compatible Android TV hardware.

TV-only vs mobile-compatible Android apps

The most important question is not simply whether your application has a closed-testing track. The important question is which device types Google Play considers compatible with the application.

An Android application can support one form factor or multiple form factors. For example, a developer may build an application specifically for Android TV, or build one application that supports phones, tablets, and Android TV.

This distinction should be checked before purchasing a testing service. A closed-testing track by itself does not guarantee that every tester device can install the application.

How Google Play determines device availability

Google Play uses the application's declared features, hardware requirements, software requirements, APK/AAB configuration, and other compatibility information to determine which devices can install an application.

For Android TV applications, Google documents the android.software.leanback feature as the mechanism used to identify TV support. If an application runs on both mobile and TV devices, Android recommends declaring the TV feature as not required. If the TV feature is declared as required, Google Play can restrict the application to Android TV OS devices.

For example, Android's documentation describes the following configuration for applications that support both mobile and TV:

<uses-feature
    android:name="android.software.leanback"
    android:required="false" />

By contrast, setting the feature to required="true" indicates that the TV capability is required, which can make the application available only to Android TV devices.

Therefore, developers should not assume that changing a setting in the Play Console after creating the application will automatically make a TV-only application compatible with phones and tablets. The application's actual technical configuration must support the target device category.

See Google's Android TV documentation for the current technical requirements.

Before you order FastTesters

To prevent compatibility problems and unnecessary refunds, always verify your application's supported devices before purchasing a FastTesters package.

Use this checklist:

• ☐ Is the application available for Android phones?
• ☐ Is the application available for Android tablets, where applicable?
• ☐ Can a normal Android phone/tablet tester open the Google Play testing link?
• ☐ Can the application actually be installed on a compatible Android phone/tablet?
• ☐ Is the app more than just an Android TV application?
• ☐ If the app supports both TV and mobile, have you verified that the mobile experience is available?

If the answer to the first or third question is no, do not assume that the application is compatible with FastTesters.

If you are unsure, contact FastTesters support before purchasing and provide the Google Play testing link. This allows compatibility to be clarified before credits are purchased and assigned.

Why having a testing link is not enough

A common misunderstanding is that if you have successfully created a Google Play closed-testing link, any tester can use that link to install the application.

That is not how Google Play device compatibility works.

The testing link identifies the testing program, but Google Play still evaluates whether the user's device is compatible with the application. A tester using an Android phone may see that the application is unavailable for their device even though the application is correctly configured in the developer's closed-testing track.

This is especially important for TV-only applications. The application can be completely valid, published to a closed-testing track, and accessible through the developer's Play Console while still being unavailable to a phone-based tester.

For this reason, FastTesters cannot determine TV compatibility simply by checking whether a customer has added an application to a closed-testing track. The developer's Play Console and the application's device configuration determine which devices Google Play allows to install the application.

What if my app supports both phones and Android TV?

If your application genuinely supports both Android phones/tablets and Android TV, FastTesters can be used for the phone/tablet portion of the closed test.

However, the customer should understand what the service is testing.

If the mobile and TV versions share the same application package, FastTesters testers can test the mobile-compatible experience as long as Google Play makes that application available to their Android phone/tablet devices.

What should TV-only developers do?

If your application is exclusively designed for Android TV, you should recruit testers who actually have access to compatible Android TV devices or TV hardware.

This is different from recruiting ordinary Android phone testers. A phone tester cannot substitute for a TV tester when the application is not available on their device.

TV-specific testing should focus on the actual TV experience, including:

• Remote and D-pad navigation
• Focus movement between interactive elements
• Back and Home button behavior
• Large-screen readability
• Ten-foot UI layout
• TV-specific media playback
• Landscape presentation
• Overscan and screen-edge behavior
• Performance on the target TV hardware

Google's current Android TV documentation specifically emphasizes intuitive remote-based navigation and designing the TV experience for viewing from a distance.

Does the Google Play closed-testing requirement still apply?

For new personal developer accounts subject to Google's testing requirement, Google currently requires a closed test with at least 12 testers opted in continuously for at least 14 days before the developer can apply for production access. The requirement is tied to the developer account and production-access process, rather than being a special FastTesters requirement.

However, satisfying the numerical tester requirement does not mean that every tester can test every type of device.

A TV-only application may still require TV-capable testers to provide meaningful testing. Likewise, if a developer chooses a phone/tablet testing service, the application must be available to those phone/tablet devices.

This is why tester count and device compatibility are two separate questions:

Closed-testing track vs device compatibility

It is useful to think of Google Play testing as having two separate layers.

Layer 1 — Testing track: The developer creates an internal, closed, or other available testing track and publishes a build to it.

Layer 2 — Device compatibility: Google Play determines whether a particular user's device is eligible to install that application.

A successful Layer 1 configuration does not override Layer 2.

For example, a developer may have:

• A valid AAB uploaded to a closed-testing track.
• A published testing release.
• A working opt-in link.
• Testers added to the testing group.

Yet a tester using a phone can still receive a message indicating that the application is unavailable for their device if the application is configured as TV-only or otherwise has incompatible device requirements.

This is one of the most important checks developers should perform before ordering phone/tablet testers.

A simple compatibility check before submitting

The safest workflow is to test your own closed-testing link from a normal Android phone or tablet before purchasing external testers.

1. Create or open your Google Play closed-testing track.
2. Make sure the testing release is available.
3. Open the opt-in link using a Google account that is not the developer account.
4. Open the link from an Android phone or tablet.
5. Check whether Google Play allows the application to be installed.
6. Launch the application and verify that the core mobile experience works.

If Google Play reports that the application is unavailable for the device, do not purchase a phone/tablet testing service yet.

First determine why the device is filtered out. The cause may be the application's declared TV requirements, hardware requirements, Android version requirements, ABI requirements, screen/device configuration, or another compatibility restriction.

Device filtering can affect tester availability

Google Play uses device compatibility information to determine whether an application can be installed on a particular device. Device filtering can therefore affect the number and type of testers who are able to join a test.

This matters especially for specialized applications.

An application might require:

• A specific hardware feature
• A specific Android version
• A TV-only software feature
• A particular architecture
• A specific screen configuration
• A device capability that ordinary phones do not provide

In these cases, simply recruiting more phone users does not solve the compatibility problem.

The correct approach is to recruit testers who actually have compatible devices.

What FastTesters is designed for

FastTesters is designed around a simple use case: developers who need real testers for Android phone and tablet applications participating in Google Play closed testing.

The service is therefore best suited to applications such as:

• Consumer Android apps
• SaaS mobile applications
• Productivity applications
• E-commerce applications
• Education applications
• Fitness applications
• Utility applications
• Social applications
• Mobile games
• Business applications
• Other applications intended for ordinary Android phones and tablets

FastTesters is not currently a dedicated hardware-testing service for specialized device categories such as Android TV hardware.

If your application requires a specific physical device to function, you should make sure that your testing strategy includes testers who own that hardware.

Avoiding a tester-service mismatch

The best way to avoid problems is to match the tester service to the application's actual target devices.

This simple distinction can prevent wasted time, incompatible testers, and unnecessary refund requests.

What if you already ordered and discover the app is TV-only?

If you have already purchased a FastTesters package and the application turns out to be unavailable on Android phones/tablets because it is TV-only, do not ask testers to install an incompatible application.

Contact FastTesters support as soon as possible.

If the application cannot be tested by FastTesters because it is outside the supported phone/tablet device category, the order should not be treated as a normal testing assignment.

Depending on the order status and applicable refund policy, FastTesters can review the situation and determine the appropriate resolution.

If you plan to publish another Android phone/tablet application in the future, keeping the purchased credit available for that compatible application can also be a practical alternative to requesting a monetary refund, subject to the service's current terms.

What developers should verify before submitting an app

To keep the process fast and avoid compatibility issues, developers should verify the following before submitting an application:

• Target device: Is the app intended for phones/tablets?
• Play availability: Can an ordinary Android phone/tablet install it?
• Testing link: Does the closed-testing opt-in link work for a compatible tester account?
• Application state: Is the closed-testing release published and ready for testers?
• Device requirements: Does the app require specialized hardware?
• TV-only configuration: Is the app restricted to Android TV?

Checking these items takes only a few minutes and can prevent a much longer troubleshooting process after testers have already been assigned.

How to find Android TV testers

Finding testers for Android TV is different from finding ordinary Android phone testers because the tester needs access to a compatible TV device or Android TV environment.

For TV-specific testing, consider recruiting from:

• Android TV developer communities
• Existing customers who own compatible TV devices
• Your internal development or QA team
• Friends, colleagues, or beta users with Android TV hardware
• Specialized testing providers that explicitly support Android TV devices
• TV-focused developer communities and forums

If you need to satisfy a Google Play closed-testing requirement and your application is TV-only, make sure the testers you recruit can actually access and install the application on compatible TV devices.

What if the app supports both TV and mobile?

If your application supports both Android TV and Android phones/tablets, you can use different testing strategies for the two device categories.

For example:

FastTesters can be used for the phone/tablet portion when the application is compatible with those devices. TV-specific validation should be performed separately with appropriate TV hardware.

Setting up a Google Play closed-testing track

Once you have determined that your application is compatible with the devices you intend to test, configure the appropriate Google Play testing track.

Google Play provides several testing options, including internal testing and closed testing. A closed test is useful when you need to distribute an application to a controlled group of testers before production release.

A typical closed-testing workflow is:

1. Open your application in Google Play Console.
2. Navigate to the appropriate testing section.
3. Create or select a closed-testing track.
4. Configure the tester group.
5. Upload your application build.
6. Complete the required release information.
7. Roll out the testing release.
8. Obtain the tester opt-in link.
9. Share the link with eligible testers.
10. Monitor tester participation in Play Console.

Google's current Play Console documentation explains that closed testing can be used to distribute an app to a controlled group and provides an opt-in mechanism for testers.

Understanding the 12-tester requirement

For new personal developer accounts created after November 13, 2023, Google currently requires a closed test with at least 12 testers opted in continuously for at least 14 days before the developer can apply for production access.

This requirement should not be confused with a requirement that every Android application must always use exactly 12 testers.

The requirement is associated with Google's production-access process for affected personal developer accounts.

Before planning your testing campaign, check the current requirements shown in your own Play Console because Google's policies and eligibility requirements can change.

Managing the 14-day testing window

If your account is subject to the 12-tester/14-day requirement, treat the testing period as a continuous eligibility period rather than something to complete at the last minute.

A good workflow is:

1. Prepare the application before recruiting testers.
2. Publish the closed-testing release.
3. Make sure the opt-in process works.
4. Recruit more testers than the minimum where practical.
5. Monitor participation during the testing period.
6. Avoid making unnecessary changes to the testing configuration.
7. Keep the required testers opted in continuously.
8. Wait until the required period has been completed.
9. Use Play Console's production-access workflow when eligible.

Recruiting exactly the minimum number of testers can create unnecessary risk. If one tester becomes unavailable or another tester encounters an eligibility problem, you may have less margin than expected.

Closed testing is not the same as professional QA

Google Play's closed-testing requirement and professional quality assurance have different objectives.

Closed testing can demonstrate that a group of real users has access to and participates in your application before production. It does not automatically provide comprehensive compatibility testing across every device, Android version, TV model, screen size, chipset, controller, or peripheral.

This distinction is particularly important for Android TV applications.

A TV application may require testing across:

• Different Android TV OS versions
• Different TV manufacturers
• Different display resolutions
• Different remote controls
• Different D-pad implementations
• Different audio configurations
• Different network conditions
• Different media codecs
• Different performance profiles

If your application has significant technical requirements, consider combining Google Play closed testing with a dedicated QA strategy.

Android TV quality checklist

Before publishing an Android TV application, review the TV-specific requirements that apply to your application.

At a high level, check:

• TV launcher: The application should integrate correctly with the TV launcher.
• Landscape layout: The experience should be designed for television screens.
• Remote navigation: Users should be able to navigate without relying on touch input.
• Focus behavior: Interactive elements should have clear and predictable focus states.
• Readability: Text and controls should remain readable from a normal viewing distance.
• Overscan: Important content should not be placed too close to the screen edges.
• Back navigation: The Back button should behave consistently.
• Media: Video and audio playback should behave correctly on supported TV hardware.
• Performance: Startup, navigation, animations, and playback should remain responsive.
• Controller support: Games and interactive applications should properly handle supported TV input methods.

Google's Android TV quality documentation contains the authoritative requirements and should be checked before release because requirements can evolve.

Common Android TV testing mistakes

1. Assuming every Android tester can test a TV app

This is the most common mistake.

An Android phone and Android TV are part of the Android ecosystem, but they are not interchangeable testing environments.

2. Buying phone testers for a TV-only application

If the application is restricted to Android TV, ordinary phone testers may not be able to install it.

3. Confusing the testing link with device compatibility

A valid closed-testing URL does not guarantee that every device can install the application.

4. Testing TV navigation with a touchscreen

A touchscreen interaction that works perfectly on a phone may not make sense on a TV.

5. Testing only an emulator

Emulators are useful during development, but physical hardware can reveal problems related to remotes, display behavior, performance, media playback, and manufacturer-specific behavior.

6. Treating the 12 testers as a complete QA strategy

The minimum tester requirement and comprehensive device coverage are different objectives.

7. Waiting until the end of the testing period to discover compatibility problems

Always verify the testing experience at the beginning of the test rather than discovering near the end that the testers cannot install or use the application.

Android TV testing troubleshooting

My tester sees "This app isn't available for your device"

First verify that the tester's device is actually compatible with the application.

Check:

• Device type
• Android version
• Required hardware features
• Application manifest requirements
• TV-only requirements
• Architecture requirements
• Play Console device compatibility information

If the application is intentionally TV-only, a phone tester is not an appropriate tester for that application.

The testing link works for me but not for my tester

Do not assume the link is broken.

The developer's device may be compatible while the tester's device is not. Test the link from the same type of device your testers will use.

My application supports TV but testers cannot install it on phones

Review the application's device requirements and manifest configuration.

If the application is intended to support both TV and mobile, make sure the TV-specific features are not incorrectly declared as mandatory for every device category.

Also check Google Play's current device-compatibility information for the application.

Can I use FastTesters for my Android TV app?

Not if the application is Android TV-only.

FastTesters currently focuses on Android phone and tablet applications. We do not currently provide a dedicated Android TV tester network or physical Android TV testing service.

If your application supports both mobile and TV, FastTesters may be appropriate for the phone/tablet portion of the test, provided the application is actually available on compatible Android phone/tablet devices.

Choosing the right testing approach

A note about FastTesters

FastTesters is included here because many Android developers search for closed-testing solutions while researching Google Play requirements.

However, the service scope should be understood clearly:

This distinction is intentional. A tester should have the appropriate device for the application being tested.

Frequently Asked Questions

Does Android TV use Google Play closed testing?

Yes. Android TV applications can use Google Play testing tracks. The appropriate testing configuration depends on the application and developer account.

Does the 12-testers/14-days requirement apply to Android TV?

For new personal developer accounts subject to Google's production-access testing requirement, the requirement is currently at least 12 testers opted in continuously for at least 14 days. The requirement is associated with the affected developer account and production-access process, not a special exemption for Android TV.

Can I use phone testers to satisfy testing for a TV-only application?

You should not assume that you can. If the application is unavailable on Android phones, phone testers cannot meaningfully test or install it. Recruit testers with compatible Android TV devices when TV testing is required.

Can FastTesters test my Android TV-only application?

No. FastTesters currently supports Android phone/tablet applications and does not provide a dedicated Android TV tester service.

What if my app supports both Android TV and phones?

FastTesters can potentially be used for the compatible phone/tablet experience. However, TV-specific behavior should be tested separately using compatible Android TV hardware.

Why can my tester not find my app on Google Play?

Possible causes include testing-track configuration, account eligibility, device compatibility, application requirements, Android version requirements, or other Google Play filtering rules.

Check the testing release, tester eligibility, opt-in status, and device compatibility before assuming that the testing link itself is incorrect.

Can an Android TV emulator replace physical TV testing?

An emulator is useful for development and basic validation, but physical TV hardware provides additional information about remote navigation, display behavior, performance, media playback, and other hardware-specific behavior.

Should I test Android TV and mobile separately?

If your application supports both platforms and the TV experience is important, yes. Treat the mobile and TV experiences as separate device-testing targets even if they share the same application package.

Can I purchase FastTesters first and check compatibility later?

It is strongly recommended to verify phone/tablet compatibility first. If your application is TV-only, do not purchase a phone/tablet tester package expecting TV testing.

Pre-purchase checklist

Before ordering any phone/tablet testing service, answer these questions:

If you answer Yes to "Is my app TV-only?" then FastTesters is not the appropriate tester service for that application.

Recommended workflow for Android developers

A reliable workflow looks like this:

1. Identify your target devices.
   Determine whether your application targets phones, tablets, TVs, or multiple categories.
2. Verify Play compatibility.
   Check that your application can actually be installed on the devices your testers will use.
3. Create the appropriate testing track.
   Configure your internal or closed-testing release in Play Console.
4. Test the opt-in process yourself.
   Use a compatible tester account and device.
5. Choose testers based on hardware.
   Phone applications need phone testers; TV applications need TV-capable testers.
6. Start the testing period early.
   Do not wait until you are close to your production-access deadline.
7. Monitor participation.
   Keep track of tester eligibility and participation during the testing period.
8. Perform platform-specific QA.
   If your app supports TV, perform dedicated TV testing instead of assuming mobile testing covers it.
9. Apply for production access when eligible.
   Follow the current Play Console process for your developer account.

Final takeaway

Android TV applications can use Google Play's testing infrastructure, but Android TV testing is not the same as ordinary Android phone/tablet testing.

The most important thing is to match the testing device to the application's actual compatibility requirements.

If your application is:

• Phone/tablet only: a phone/tablet tester service can be appropriate.
• Phone/tablet + TV: use phone/tablet testers for the mobile experience and perform separate TV testing for TV-specific functionality.
• TV-only: recruit testers who have compatible Android TV hardware.

And specifically for FastTesters:

Checking this before purchasing testers is the simplest way to avoid an incompatible testing order.

Official Google resources

• Google Play Console — Testing requirements for personal developer accounts
• Google Play Console — Set up an open, closed, or internal test
• Android Developers — Create and run a TV app
• Android Developers — TV app quality
• Google Play Console — View and restrict compatible devices

Related reading

• Google Play Closed Testing Guide
• Google Play Closed Testing Requirements
• Google Play Testing Tracks Explained
• How to Get Testers for Google Play

---

Article scope note: This article is an educational guide to Android TV applications and Google Play testing. Google Play requirements, device compatibility rules, and developer-account policies may change. Always verify the latest requirements in Google Play Console and the official Android documentation before relying on a specific requirement.