If you develop on the Android platform and haven't had a chance to try out the new widgets introduced in Android L Preview this will be a very interesting presentation for you; find out from my experiments how the new RecyclerView stacks up against the view it should replace. If Android is not your game, you will still learn a few things regarding lists on mobile and what Android is like for developers on the platform.
Presented at Codecamp Iasi Autumn 2014
Android has a fragmented ecosystem. There are devices out there with square screens or even no 3G antenna. It’s impossible to test on all of them. But if we write automated tests, then maybe we could run these tests on hundreds of real devices in the cloud. Let’s compare Espresso to Appium and Amazon Device Farm to Firebase Device Lab and see which of these we like more.
Unele prezentari sunt mai usor de urmarit, alte sunt mai greu de urmarit. A ta cum va fi? Vino la acest training si cu siguranta vei ramane cu cateva idei bune. Fie ca ai licenta anul acesta, fie ca vrei sa tii o prezentare la urmatorul eveniment IT local, vino sa discutam despre elementele unei prezentari bune.
Prezentarea a fost tinuta in cadrul ITst, la Facultatea de Informatica, Cuza, Iasi.
Slides for the "Performance Tools" presentation for Droidcon Bucharest. It is a talk about Traceview, Systrace and Battery Historian, with some practical, or better yet impractical examples.
Description:
The Android ecosystem has a lot of tools to help us out when it comes to development. We all use Android Studio, gradle and adb, for instance. We need to, as these are essential tools for building our products. But what about the tools that help us diagnose problems in our apps? This session is all about asking 2 very common questions:
Why is my app stuttering or dropping below 60fps?
Why are my users telling me that my app drains their batteries?
Most of the times solving a problem means asking the right questions in order to find the right answers. So starting from these 2 questions, with concrete problem-code examples we will be using tools from Google to find our answers.
I don't want it to be a secret, so I'm telling you that the tools we will be using the most will be Traceview and Battery Historian. We will also be looking at Profiling GPU Rendering and Debugging Overdraw.
I know that these tools might look a bit scary or dull but I promise to keep it simple so that you walk away with information you can use at work the next day.
If you develop on the Android platform and haven't had a chance to try out the new widgets introduced in Android L Preview this will be a very interesting presentation for you; find out from my experiments how the new RecyclerView stacks up against the view it should replace. If Android is not your game, you will still learn a few things regarding lists on mobile and what Android is like for developers on the platform.
Presented at Codecamp Iasi Autumn 2014
Android has a fragmented ecosystem. There are devices out there with square screens or even no 3G antenna. It’s impossible to test on all of them. But if we write automated tests, then maybe we could run these tests on hundreds of real devices in the cloud. Let’s compare Espresso to Appium and Amazon Device Farm to Firebase Device Lab and see which of these we like more.
Unele prezentari sunt mai usor de urmarit, alte sunt mai greu de urmarit. A ta cum va fi? Vino la acest training si cu siguranta vei ramane cu cateva idei bune. Fie ca ai licenta anul acesta, fie ca vrei sa tii o prezentare la urmatorul eveniment IT local, vino sa discutam despre elementele unei prezentari bune.
Prezentarea a fost tinuta in cadrul ITst, la Facultatea de Informatica, Cuza, Iasi.
Slides for the "Performance Tools" presentation for Droidcon Bucharest. It is a talk about Traceview, Systrace and Battery Historian, with some practical, or better yet impractical examples.
Description:
The Android ecosystem has a lot of tools to help us out when it comes to development. We all use Android Studio, gradle and adb, for instance. We need to, as these are essential tools for building our products. But what about the tools that help us diagnose problems in our apps? This session is all about asking 2 very common questions:
Why is my app stuttering or dropping below 60fps?
Why are my users telling me that my app drains their batteries?
Most of the times solving a problem means asking the right questions in order to find the right answers. So starting from these 2 questions, with concrete problem-code examples we will be using tools from Google to find our answers.
I don't want it to be a secret, so I'm telling you that the tools we will be using the most will be Traceview and Battery Historian. We will also be looking at Profiling GPU Rendering and Debugging Overdraw.
I know that these tools might look a bit scary or dull but I promise to keep it simple so that you walk away with information you can use at work the next day.
17. public class ToDo extends SugarRecord<ToDo> {
String text;
public ToDo() {
}
public ToDo(String text) {
this.text = text;
}
}
ToDo unu = new ToDo(context, “unu”);
unu.save();
18. Alte optiuni, poate chiar mai bune
- ActiveAndroid
- Ollie
- Realm
- Schematic
20. Daca folositi SQL pe Android pentru
prima oara, folositi SQL normal, fara
nimic. Va ajuta sa intelegeti.
21. Level 1:
- Aplicatie de TODO cu ADD, REMOVE.
Level 2:
- Adaptorul listei sa utilizeze un cursor
Level 3:
- Faceti o legatura one-to-many intre todo si persoane. Un todo
poate avea mai multe persoane.
- Sa nu aveti nimic costisitor pe threadul UI
Realm special: Faceti ca interogarile sa se intample pe alt thread.