Sebastiano Gottardo
Jun 24 · 1 min read

It depends on your situation: how many developers in your team, how much of an annoyance using pure SQLite is to the team, how often you need to touch the database, what’s your current architecture, etc. While I can’t say what’s best for you, I can share how it was better for us: 6 developers and counting, finding extremely annoying to have to deal with Cupboard (learning curve, basic documentation), pointing out the lack of reactiveness for our future architecture. It seemed a no-brainer.

    Sebastiano Gottardo

    Written by

    Engineering Manager + Android Engineer, GDE