When developers travel, we usually prepare the obvious things.
Laptop charger.
Power adapter.
Cloud backups.
Password manager.
2FA access.
Offline copies of important documents.
But there is one dependency that is easy to underestimate until it breaks:
mobile internet.
A trip to China makes this especially obvious.
Not because China is hard to travel in, but because so many basic interactions are mobile-first: navigation, translation, ride-hailing, hotel communication, ticket confirmations, payments, and sometimes access to the tools you normally use every day.
So I started thinking about travel connectivity the same way I think about a small production dependency.
Not glamorous.
Not exciting.
But if it fails, everything around it gets annoying fast.
China is a good test case for travel connectivity
China is not just “another country where you need data.”
It is a place where your phone becomes a practical interface for the trip.
You may need it to:
translate signs, menus, and messages
find the correct metro exit
call a ride
open booking details
check train times
message a hotel or host
use payment or identity flows
access services that may behave differently from home
None of these tasks are special on their own. But together, they create a simple rule:
do not make mobile internet something you solve after landing.
That is the same kind of thinking I use with software projects. If a dependency is critical at startup, I want it configured before runtime.
My pre-flight connectivity stack
Before a China trip, I would prepare the phone like this:
connectivity/
esim-ready
main-sim-active
offline-maps
offline-translator
vpn-tested
booking-screenshots
hotel-address-localized
payment-apps-installed
emergency-contacts-saved
This is not a fancy setup. It is mostly boring.
But boring is good when you are arriving tired, carrying luggage, and trying to get from the airport or train station to your hotel.
The main idea is simple: the phone should already be useful before the first Wi-Fi login screen appears.
Where eSIM fits into this setup
An eSIM is not magic. It is just a more convenient way to provision mobile data without swapping a physical SIM card.
If I were comparing providers before the trip, I would check a few options rather than choose one randomly at the airport. Skyalo is one provider that can fit naturally into that research step, especially if you want to browse travel eSIM plans before flying.
For China, that convenience matters.
Instead of landing and searching for a local SIM option, you can prepare a travel data plan in advance, install the eSIM before departure, and turn it on after arrival.
That is why I see eSIM less as a “travel hack” and more as a configuration step.
Something like:
mobile_data_provider = selected_before_departure
activation = on_arrival
fallback = hotel_wifi
main_number = kept_for_sms_and_banking
If I were comparing providers before the trip, I would check a few options rather than choose one randomly at the airport. Skyalo is one provider that can fit naturally into that research step, especially if you want to browse travel eSIM plans before flying.
That is the most reasonable way to mention a provider in this context: not as the main point of the article, but as one possible tool in the setup.
Things I would test before departure
The most useful checklist is not long.
- Check eSIM support
Not every device supports eSIM, and some phones have region-specific limitations. This is the first thing I would verify.
- Keep the main SIM active
Even if you use a travel eSIM for data, your main SIM may still be needed for bank confirmations, 2FA, or important SMS.
- Install apps before traveling
Do not wait until arrival to install tools you might need. App availability, network conditions, and account verification can all become annoying when you are already abroad.
- Download offline fallbacks
Offline maps and offline translation are not perfect, but they are very useful when something breaks.
- Test VPN before the trip
If you rely on services that may not work normally in China, test your VPN before departure. Do not make VPN setup an airport task.
- Save hotel addresses in two formats
I would save the hotel address in English and Chinese, plus screenshots. This helps with taxis, check-in, and offline situations.
How much data would I plan for?
For a short trip, 3-5 GB may be enough if you mostly use maps, messages, translation, and light browsing.
For a week, I would personally feel better with around 10 GB.
For remote work, hotspot usage, frequent video calls, uploads, or multi-city travel, 20 GB or more becomes more realistic.
The point is not to overbuy. The point is to avoid optimizing for the smallest possible plan when the cost of running out of data is high.
In China, mobile data is not only for scrolling. It supports the basic UX of the trip.
A simple failure model
I like thinking in failure modes.
What happens if mobile data does not work?
failure: no mobile data after arrival
impact:
cannot load map route
cannot message hotel easily
cannot call ride smoothly
translation becomes harder
payment and verification flows may break
airport/station Wi-Fi becomes single point of failure
The fix is not complicated:
mitigation:
install eSIM before departure
keep offline maps
save screenshots
keep main SIM available
test VPN and key apps
have hotel address saved locally
Again, not exciting. Just practical.
China-specific places where this matters
In Beijing, distances are large and live navigation helps a lot.
In Shanghai, switching between metro, walking, taxis, restaurants, and neighborhoods is much easier when your phone is connected.
In Xi’an, translation and maps are useful around the Muslim Quarter, city walls, stations, and the Terracotta Army area.
In Chengdu, food is a major part of the trip, and translation can save you from ordering completely blind.
In Guilin or Yangshuo, having mobile data outside the biggest cities can be more valuable than expected, especially for routes, drivers, and day trips.
Final thought
For China, I would treat connectivity as part of the travel stack.
If you usually research connectivity before a trip, you can also find more practical notes on eSIMs, roaming, and mobile internet abroad in the Skyalo blog.
Not because every trip needs to become a technical project, but because some dependencies are easier to configure before you need them.
Mobile data is one of them.
If your phone is ready before you land, the first hours of the trip become simpler: maps work, translation works, hotel details are available, messages go through, and you are not relying on random Wi-Fi at exactly the moment you need the internet most.
That is the quiet value of preparing an eSIM in advance.
It is not about being online all the time.
It is about making sure the tools you depend on are ready when the trip starts.
