Home

Introduction

Goals

Data persistence on Android can be tricky. In our applications, we always used handwritten SQL commands to work with the database directly. This was mainly because any ORM for Android seemed too difficult to setup, or was too slow, because of reflection. And that is why we built Torch. It is simple to setup, easy to use and very fast, as it does not use reflection, but annotation processing in compile-time.

Features

• From 0 to 60 in seconds: Adding Torch to your project is a piece of cake. There is not much you would need to learn and you can start using it immediately.
• User-friendly API: We've spent many sleepless nights drafting the API to match our high requirements to deliver easy to use interface.
• Superior performance: Thanks to annotation processing, which happens when you compile your code, you won't waste your processing time on slow Java reflection. Nothing is dynamic, everything it precompiled.
• Compile time safety: Many ORM libraries let you work with fields of your entities using their names as Java strings. We believe that this is a disadvantage, because you can't let the compiler help you check if you didn't refactor the field away, by changing its name or removing it. With Torch you will reference the fields in compile time safe manner.

What to do next

• If you like the idea of an easy data persistence for your Android application, Jump right in!
• Found a bug? You can either report it to the issue tracker, or if you know how to fix it, send us a pull request with the fix! We will appreciate any feedback and contributions to the project!