Paper is a fast NoSQL data storage for Android that lets you save/restore Java/Kotlin objects using efficient Kryo serialization. Class structure changes handled automatically.

• (!) Fixed crash on data migration when switching lib from 1.x to 2.x
• (!) Fixed possible data loss on failed read attempt.

• (!) Fixed exception causing data corruption on Android N+ (happens if targetSdkVersion=25+);
• Get timestamp of last update using book.lastModified(key);
• Set log level for internal Kryo serializer using Paper.setLogLevel() or book.setLogLevel() ;

Thanks @aaronpoweruser and @fiskurgit for contrib!

compile 'io.paperdb:paperdb:2.1'

Should be initialized one time in onCreate() in Application or Activity.

Paper.init(context);

It's OK to call it in UI thread. All other methods should be used in background thread.

Save data object. Paper creates separate data file for each key.

Paper.book().write("city", "Lund"); // Primitive
Paper.book().write("task-queue", queue); // LinkedList
Paper.book().write("countries", countryCodeMap); // HashMap

Read data objects. Paper instantiates exactly the classes which has been used in saved data. The limited backward and forward compatibility is supported. See Handle data class changes.

String city = Paper.book().read("city");
LinkedList queue = Paper.book().read("task-queue");
HashMap countryCodeMap = Paper.book().read("countries");

Use default values if object doesn't exist in the storage.

String city = Paper.book().read("city", "Kyiv");
LinkedList queue = Paper.book().read("task-queue", new LinkedList());
HashMap countryCodeMap = Paper.book().read("countries", new HashMap());

Delete data for one key.

Paper.book().delete("countries");

Completely destroys Paper storage. Requires to call Paper.init() before usage.

Paper.book().destroy();

You can create custom Book with separate storage using

Paper.book("custom-book")...;

Each book is located in separate file folder.

Returns all keys for objects in the book.

List<String> allKeys = Paper.book().getAllKeys();

Class fields which has been removed will be ignored on restore and new fields will have their default values. For example, if you have following data class saved in Paper storage:

class Volcano {
        public String name; // I like Eyjafjallajökull
        public boolean isActive;
    }

And then you realized you need to change the class like:

class Volcano {
        public String name; // I like Eyjafjallajökull
        // public boolean isActive; removed field, who cares about volcano activity
        public Location location; // New field
    }

Then on restore the isActive field will be ignored and new location field will have its default value null.

Use transient keyword for fields which you want to exclude from saving process.

public transient String tempId = "default"; // Won't be saved

• Keep data classes:

-keep class my.package.data.model.** { *; }

alternatively you can implement Serializable for all your data classes and keep all of them using:

-keep class * implements java.io.Serializable { *; }

Paper is based on the following assumptions:

• Saved data on mobile are relatively small;
• Random file access on flash storage is very fast.

So each data object is saved in separate file and write/read operations write/read whole file.

The Kryo is used for object graph serialization and to provide data compatibility support.

Running Benchmark on Nexus 4, in ms:

• Circular references is not supported

• AppDialer – Paper initially has been developed to reduce start up time for AppDialer. Currently AppDialer has the best start up time in its class. And simple no-sql-pain data storage layer like a bonus.

Copyright 2015 Aleksey Masny

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

   http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.