Not necessarily. Just because you are accessing records against a DB on the server does not mean you need a DB of any kind on the client side (your phone).
If you do not need to store the data on the phone, there is no need to keep in SQLite. If you just want to display the data on your phone, you would be better off defining common access paths to the data on the server (all records that match a certain date or region, all records pertaining to a particular business
unit, etc), building the ability to access that data from a REST-based web service (returning the data using the JSON notation) and calling the web service from the phone (Spring offers their RestTemplate client).
So the first question you need to ask yourself. If a user brings up the app on their phone and there is no network connection, do they need to see the last good set of data brought across from a previous connection? If not, no need to store it. If you do need to display the last best set of data, ask yourself, how sensitive is the data? If the person lost the phone and someone accessed the phone and the data, is that loss critical?
