Ok noted. As long as tithing does not require to have full blockchain data loaded, it is possible to implement. Remember that mobile wallet only stores block headers and your own wallet's UTXOs and TXs.
I think you can (given your availability) port the GetTitheParams function(s) (just the math function(s) like quantize, not the UpdatePogPool stuff) into the mobile wallet, and call the Pool API for the pindexBestHeader->chainTip() POG difficulty level (IE 0-65535) (only because the pindex during sync wont have your current diff since the blocks arent stored but instead computed in the large client), once you have that int you can then call for the GetTitheParams, and that gives you the 3 things we can quote the user (age, max, min).
The POG transaction does not require, but we should, transmit the <nickname> XML and the <tither> address in the ".sTxOutMessage" field - I dont know if you have implemented that field in the mobile client yet, would that be hard to add that field to the broadcasted transaction? Then you would need to ask them for their nickname somehow during setup (not sure if there is a config in there). It actually is OK to skip those two as users will receive POG payment rewards back to the sending address but I still recommend us going the extra mile to add the ability to send the message, because it is frowned upon to send rewards back to the change address (in addition a lot of clients try to anonymize the change address, and also it creates more spam, IE mobile user jumping around in the pog pool with many addresses etc).
At this point, the tithe should be accepted in the pogpool, so I think it should be doable.... Of course we should talk more about our apple situation as what is the use in doing all this if we cant even get listed in the Apple store.
On a different subject, I did comment out the AboutRole and chat now appears; I will be checking in later today (working on the Writing to Orphan UI now).