A modern programming language that makes developers happier.

kotlinlang

I've been using SqlDelight in my Android app for a while now, and I've been using a hodgepodge of tables and views to retrieve data for my screens.

I'm now considering defining a view per screen, and sort of treating it as a repository layer. Is that a bad idea, and if not, what are some potential problems to look out for?

One issue that I'm anticipating is that migrations are going to get more difficult in terms of figuring out which views need to be recreated, and then having the migration actually recreate them (in terms of inflating the migration file size)