In libdx you don't use a sqlite you simply use the preferences they offer. They get stored on android in the SharedPreferences and on desktop in an xml. For storing the questions i would hardly recomend to use a xml format and parse it on runtime. Maybe even encrypt/decrypt it.
To give you an idea what we are talking about. You create an XML maybe with an editor you just shortly hacked. Parse it into an good looking xml format. For example this is one of mine (not for questions but i think you get an idea of how to use the idea)
<root>
<quest1 id="1">
<name>quest1_name</name>
<description>quest1_description</description>
<subq type="KILL" monster_type="death" count="1" reward="15" />
</quest1>
<quest2 id="2">
<name>quest2_name</name>
<description>quest2_description</description>
<subq type="KILL" monster_type="silverbat" count="25" reward="45" />
</quest2>
</root>
Now you create an QuestionManager which you start while starting your app. And this does parse all childs of the root Element into an Question. So your Question has an constructor which takes an Element. This is the loading inside of the Manager:
public void loadQuests() {
XmlReader r = new XmlReader();
Element e = null;
try {
e = r.parse(Gdx.files.internal("quest/quest.xml"));
}
catch (IOException a) {
}
if (e != null) {
for (int i = 0; i < e.getChildCount(); i++) {
m_quests.add(new Quest(e.getChild(i))); //has reference to the core class
}
}
}
And the Quest (in this case it's not a question i know!)
public Quest(Element xml) {
setID(xml.getInt("id"));
setTitle(xml.getChildByName(Quest.NAME).getText()); // final static string
setDescription(xml.getChildByName(Quest.DESC).getText());
}
Even a thousand of questions shouldn't be such a big deal. In case it does let your Game lag on startup put the loading in an sperat thread for it and don't start using the QuestionManager till the loading is done or you synchronize the list / array of question. Also use the collections of libgdx to have a better performance and less garabage collecting.
If you really want to use a sqllite on Android go for Interfacing with platform specific code. But you cant use that on desktop than! So you need to create a desktop and an android implementation then.