ATLAS: In-App use, not a Link to Web-App

André Kage

I would prefer in-app use with its own tab. Using it with a link to the web-app is not satisfactory

Jonathan Sheehy

Logos Mobile's maps functionality is essentially useless on mobile phones. (The Atlas function is absolutely not made for mobile phones. A large portion of the screen is constantly covered by menus! And I don't want to leave the app for a web browser every time I want to see a map, in any case: I have a number of atlases in my library with good maps in them -- right there in Logos.)

It's hard for me to overstate how surprised (in a bad way) I was when I discovered how bad the map functionality is in Logos on a phone. I genuinely thought I'd missed something, so I experimented, went searching forums, etc. But no, it turns out I was right: Usable map functionality for mobile phones is just not there. (But somebody please correct me if I'm missing something!)

I have several atlases in my library with excellent maps in them. Surely Factbook place entries could simply search my atlas resources for relevant maps? That would be 1) excellent and useful, and 2) what I naturally expected when I started looking up places in Factbook.

P.S. Olive Tree have got this right in their app.

P.P.S. A workaround: Create a 'collection' (using the desktop app) that contains all your atlases. Then on mobile, when you want to see a map, open a search, set it to search the Atlas collection you made, and type in the place you're looking for. That will mostly do the trick. But it's a heap of taps required every time you want to look up a map (given you've already paid for atlases) of a place that shows up in a text you were reading. I expected Factbook to look after this for me in a couple of taps.