He began to write the first thing that came to mind - a book with recipes. The bottom line is that the main screen is a ListView with headers and an "add" button. When you click on "add", another activity opens, in which the name of the recipe and its description are entered. From this data, a new object is created:
public class Recipe implements Parcelable{ private String recipeName; private String recipeDescriptions; public Recipe(String recipeName, String recipeDescriptions) { this.recipeName = recipeName; this.recipeDescriptions = recipeDescriptions; } } //дальше реализация Parcelable When you click on Item in ListView , this recipe should be edited. At the moment, a new Activity implemented, in which recipeName and recipeDescriptions are transferred and entered into the corresponding EditText 's. Everything is edited and saved perfectly. However, when there was a question about saving objects, to restore them when the application was loaded, I just got stuck. Is it really impossible to do without a database? I think I suffered the wrong steppe.
Tell me, please, how best to implement storage and recovery at boot? Maybe I need to completely revise the concept of the application and do everything in any other way? Maybe you do not need to do the Recipe class at all, but do everything with String ?
NoSqlsolutions fromRealm- it is fashionable and cool. You can store objects directly, no messing around with SQL`. - Yuriy SPb ♦RecyclerViewable to work with complex and massive lists better thanListView, use it better, it is also more convenient. It definitely won't hang with him - FlippyRecipemodel can be replaced byPair<String, String>, but it's worse ... It's better to take the name throughgetRecipeName- Flippy