Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Search for "Android samples". They have a repo with them.
Search for SqliteOpenHelper or preferably Room examples.
If you want to pass actual instances between activities, I think you won't escape static fields. In that regard you might as well make singleton Dao.
You can take advantage of your "Application" class, to initialize shared instances, that require either Context or teardown. People often do that.
I you want a bit better DI, take a look at Dagger library.
I suggest you make a single Activity application in combination with Dagger.
I started looking into building my Android app but wanted to see if I could get a refresher on a few things. The starter template for the Nav Layout isn't exactly functional.
So first question is anyone know any resources like an actually functioning demo project.
Also I need DB access but want to open any db file given the *.db path and the DAO should be persistent, share across all fragments/activities. What would be the best design, way of doing that in Android though.
I don't think you can pass the object between activities but what about fragments. I'm thinking the main app opens the DB and then can pass a DAO Interface to all the fragments to use?
question