Four things, in order of how often they go wrong. A portal login, meaning Xtream Codes host, username and password, so the app can pull live, VOD, series and the guide together rather than a flat list. Guide identifiers on each channel that match entries in the guide file, or the schedule stays blank on those rows. Group names that describe real categories instead of dumping everything into one bucket, since groups are how you make a huge catalog usable. And an archive or catch-up flag, without which the app cannot offer to replay a program that already aired. None of these are settings you can add yourself; the service sets them.

1. 1Portal login rather than a downloaded playlist file
2. 2Guide identifiers that match on every channel row
3. 3Meaningful group names, not one giant category
4. 4An archive flag where catch-up is offered

Because video and schedule travel separately. With a portal login the app normally pulls both, but three things break the link. The service may publish the guide at its own address, so the app needs that URL added by hand. The channel rows may carry no matching identifier, which shows as a populated guide for some channels and an empty one for others. Or the refresh interval has not come around yet on a large catalog, where the first pull can take minutes. Force a manual guide update first, then check whether the gaps are universal or partial. Universal points at a missing URL; partial points at identifiers the service has to correct.

1. 1Force a guide refresh before changing anything else
2. 2All channels blank: the guide address is missing
3. 3Some channels blank: identifiers do not match

Yes, and this catches people out. A recording is an active stream from the service's point of view, so a scheduled record occupies a connection for its whole duration exactly as a viewer would. On a tier with two connections, one recording leaves one live viewer. On a five-connection tier the same recording is barely noticed. Plan around it: check your tier before scheduling back-to-back recordings across an evening, and remember that a series rule can start a second recording while the first is still running. Our tiers run 1 to 5 simultaneous connections, installs are unlimited, and the count applies only while something is actually streaming.

1. 1One recording equals one active connection for its full length
2. 2Series rules can overlap and consume two at once
3. 3Installs are unlimited; only live streams count

Larger than most, but not without limits. Player apps keep the entire visible channel list in memory, and above roughly 18,000 entries they slow down, stutter on the guide and eventually crash. A catalog of 54,000+ channels across 190+ countries is far past that, which is why the first job after adding a playlist is hiding groups rather than watching anything. Hide every country and category you will not open, and the guide redraws faster, search returns quicker, and the crashes people blame on the service disappear. Nothing is lost by hiding a group; it comes back with one toggle. Treat this as setup, not troubleshooting, and you skip a fortnight of frustration.

1. 1Roughly 18,000 visible channels is the practical ceiling
2. 2Hiding groups is reversible and instant
3. 3Do it before judging the service's performance

Interface features, not stream quality. Multiple playlists, recording, a richer guide layout and scheduling live behind the paid tier of the player, and they are useful if you want them. What none of them touch is bitrate, codec or the origin server, all of which belong to the service. If a channel freezes at peak on the free tier it will freeze identically afterwards. Keep the two decisions separate: pay for the app because you want its features, and judge the service on figures it publishes. Ours are 99.99% uptime, about 53 minutes across a year, 1-5 connections, and a 7-day money-back window on plans.

1. 1Paid app features are interface features
2. 2Bitrate and stability stay with the service
3. 3Judge the feed on published numbers, not app tier