Autopilot runs Google Earth maps within the app.
However, you can plan it offline in Google Earth and load it into the Autopilot app as a KML or KMZ file saved from the path tool you made it with and it will take doing a flight plan that way. The big but here is some of those Google Earth path tools that make up a pre-planned route can be huge and then the app itself is bogged down in processing it. Same for Litchi if you do it offline and load into it. A lot of tight turns in Google Earth's path tools will create a whole lot of drop-downs and subsequent waypoints and the apps will protest in speed verses doing it on the app itself. Once you get the KML/KMZ loaded into the app you can end up with a 1,000 waypoints off Google Earth depending on the path tools resolution when it does its thing (Which can also result in a very bad flight path too!). Then a lot of cleanup is needed. Easier and faster to do within the app, imho.
I have an animated GIF that demonstrates how a KML/KMZ pre-planned flight can go bad here in steep terrain:
http://www.phantompilots.com/attachments/flight-plan-in-google-earth-gif.64167/ You can download the GIF and play over again it on your Photo viewer and watch the red arrow (Your drone) disappear into the
inside of the mountain and reappear on top, whereas the G.E. path tools shows the flight pattern should be on top of the wall.
Imho, these app tools seem to work better in 2D than 3D with a Z-axis involved. Very hard to get meaningful info on a vertical stack of waypoints, etc. That or relegate them to flatland areas and be careful about steep canyon terrain, buildings, etc.