Several of our collaborators are using AutoLit from their phones. They have reported difficulty accessing the include button when screening. @Jeffrey Johnson.
In general, we don’t recommend using AutoLit from mobile; there’s a lot of pages we haven’t built responsive to that screen size. A big part of our rationale is that there’s a lot of information density that makes the use of a smaller screen impractical.
If a large number of users request this feature, we can update our layouts to be more mobile-friendly, but in the meantime, my recommendation is: don’t use AL on mobile.
If it’s an infrequent or one-time thing, switching your phone’s browser to view the site in desktop mode will work much better than trying to squash the site into a mobile viewport.
@Kathryn Cowie I’m so glad you’re bringing this up. I would love a mobile version of NK. Unfortunately it will take a ton of dev time to build a truly mobile friendly version of site. As you can imagine, to make the mobile experience actually good, we’d have to reimagine how a ton of different features work.
I’m not going to say never, it’s just matter of time and priority, but it could be quite awhile.
After a little more internal discussion, we’re thinking that while we won’t immediately plan to make all of AutoLit mobile-friendly, we can start with the high volume, high value AL pages: screening & tagging.
We would detect screen size and create a different layout in these environments; it would probably involve a reduced/simplified feature set.
We launched mobile AutoLit in 1.23.0; while it covers basic screening, tagging, and inspector-like searches, we don’t curently have the vision for AL to be fully featured on mobile. Give it a try and let us know what you think!