@webiscore For now you can modify the ons-page back button handler since it has higher priority that the navigator one. You can use setDeviceBackButtonHandler(callback) and getDeviceBackButtonHandler().
@munsterlander Thank you very much for your prompt and accurate reply, for the very interesting doc reference to the plugin development (exactly what I was looking for) and your final suggestion about the IDE that I’ll try to follow.
@Abiraman-Ramanathan That is the correct behavior in order to manage memory correctly. If you are not loading millions of records or images, you could use an array to store your results client side and load from that. Technically, the results object would not be overwritten if you call your DB once and then use that to load the list as you go.