An atom cpu is based on x86 architecture as far as I know. If you’d be using meteor universal it might not work, but with plain meteor and cordova you can compile to either ARM or x86. The one cordova android app I’m working on has both the ARM and x86 version in the play store, when you download it with atom-based hardware it would install the x86 version, if not it’d install the ARM version.
Hope this answers your question, if not please clarify a bit more
I don’t think GroundDB uses a Meteor server at all - it just uses localstorage to store your data in the browser.
So I don’t think you need to be concerned about where a Meteor server can run.
In fact I’m pretty sure it’s impossible to accidentally run a web server in your Meteor client app, so you probably never need to worry about it unless you have really put in a lot of effort to work around the system.
Ground DB simply (i’m sure its not simple but…) hooks in to your collections and stores locally until the server is available (if you have a server that is), the “Client” generated by meteor is a web app so will run in your browser regardless of processor architecture. If your wrapping your app in Cordova (Meteor add-platform android) then you will also be fine as long as you are not using any cordova plugins that don’t support that arch ( unlikely in my exp…)