Android Development | Part 2 Architecture of the app After learning basics of android framework about activities, fragments and its states, we decided to create first version of an app. It consisted of several activities which were designed to communicate with each other (e.g. sending ids or string names of chosen items). As it turned out, there is no need of creating separate activity, especially for a simple app like planner. Moreover, switching between two activities is longer than two fragments. More detailed debate activities vs fragments described in this StackOverflow question. Thus, it was decided to leave ourselves with one activity (basically "main activity") and several fragments for each page(e.g. home screen with rooms, room fragment, addItem and AddRoom fragments). Along with fragments it was suggested to add view adapters to accommodate standard android LinearLayout and GridLayout Views, thus creating the following hierarchy: In both cases(fragment-...
Android Development | Part 1 Update: Android app already created and available via this link In this post series I will be describing my experience in learning Android development using Java. Me and my friend recently decided to develop some basic android application sort of TO-DO list/scheduler that will manage your cleaning work at home. The sample window of this app may look like this image bellow: So, how to begin? What I should learn first? That's kind of questions I am still asking myself :) Android Studio The most famous IDE fo Android development, however it is known to have some bugs. Android application consists of two parts: code and xmls. XML works as HTML for a web app, containing texts, buttons, image objects etc and located in res folder. The main notion in Android is Activity which as an atomic element of an app. Along with Activity android creates XML related to it. In order to relate objects on this XML layout use findViewById(R.id.some_id_fromXML) , wh...