A couple of things that helped me understand this video a bit better: 1) doing the fella's crash course and building a couple of command line apps 2) don't copy exactly what he is doing. Make an app with a similar concept (e.g. an app a waiter would use to note down food / drink orders) change the variable names and the names of the files, this way you have to figure out what is going on. The more different you can make it while keeping the same basic elements, the more it will make sense to you after building it
This has always given me the best results. nothing like typing all of this out but not *really* knowing why. By taking your suggestion, you can begin to connect the *why* dots on all of these concepts.
In my opinion it would be more educational, if you showed how the app works part by part in the emulator instead of coding everything at once and showing the end result just at the end. Otherwise, very good tutorial!
Same. I wish he would rather go by explaining and mostly showing them even what happens when things don't add. I mean the Adapter class or etc, that he used in his code. So that, it at least makes sense why things needed to be written.
Its not complex, its dumb. Design patterns should not be used for every possible piece of code. Mainly the java people are to blame for bringing this garbage onto the world. Most people are fed up with it and this is why languages like Go and Rust are on the rise.
Thank you for actually teaching stuff Most beginner tutorials out there just go all in expecting people to know how Android Studio's styling works even when they're aimed at beginners and i've watched half of the video so far and i'm understanding everything EDIT: Nevermind, i lost all track of anything once he got over the styling and i already know other programming languages well
@@FlooferLand Ah bummer. I decided to do it the old fashioned way and got a book, read it and now I know alot that most tutorials don't teach. They'll claim to give you tutorials and by the end you'll be a dev.I Its a lie. There are plenty of things you need to learn. Anyway, i hope to see you back again in the dev world.
Thank you for your videos. I've been struggling to find good kotlin tutorials, until I found this channel. You're very clear, to the point, and I understand it when you explain it. I come from a long, strictly Python background and the transition isn't easy.
@@Tobi9012 Excellent tutorial! I was leaning back and forth between Dart and Kotlin and casually learning both, simultaneously. Dart just "clicked" right away but I kept struggling with Kotlin's syntax. This guys knows how to explain it.
If you're just getting into android dev and this video confused you like it did me, its because this is not the default way to make UIs in android anymore. The thing now apparently is to use jetpack compose to create your UI entirely through kotlin instead of using XML.
I don't know why, but I feel like android development is extremely complex unnecessarily compared to web development. You have to write so much code to print so little.
You are completely correct. I had the same feeling. Android is unnecessarily complex, with too much OOP, hexagonal architecture, and so on just to do a simple screen...
You dont really explain what a lot of the functions do after the half point of the video. Theres also a major issue at 47:40 where you cant continue to follow along because it wont let you link tvTodo and the other var
You've made an excellent video. It's a shame the same can't be said for Android's development platform. This is so complex for what could be done in a few lines of HTML. But again, thanks for the video. You couldn't have done a better job.
Wow! Great Video. But the android programming needs horrible actions with lots of referencing, etc. Looks like building a nuclear recator to boil a cup of tea to me :)
@@electrocarbid That's kinda what I thought after watching the first 20 minutes. Maybe I'll watch the rest later. Or find a different tutorial. Visual Basic: 1. Run VB. 2. Double click command button in the toolbox to place a new button on the blank form. 3. Double click the button to view the code window. 4. Type MsgBox "Hello world". 5. Press F5 to run the program. 6. Click No (you can save it later) 7. Click the button. Done.
Great video! at the minute 47:12, my editor does not detect the tvTodoTitle nore cbDone objects defined in the item_todo.xml, because of this I cannot complete the apply function. Any idea about what I missed? (I am an absolute beginner)
@@vinay_dias yeah me too...I currently work with flutter but I want to get started on the MERN stack because almost all business that need an application would need a website first.. That's I'm confused whether to do MERN and put flutter on hold.. what do you think?
Just a tip: take pauses between thoughts and sentences. It’s okay to give the listener time to digest the information, and would help you gather your thoughts for more articulate and meaningful delivery.
Very nice, very easy to understand for those who interacting with Android Dev for the first time, of course u have to listen to what he said so you can understand it, not to skip the session
I felt bad when I heard Java support is dyeing, but I know I have to learn Kotlin as a beginner despite being Android dev for over 7 years. Great tutorial, this should get me started.
late to this party, lol, Java is not dying it's one of the top languages behind Python and Javascript. Many large companies still rely heavily on it due to it's major support. They just released Java 20 back in March, if anything this language is growing. It might start dying in 25 years but even then I highly doubt it
Literally, I followed the course from start to end (yes, I had to install Android Studio) and got the app working (well, I had to read the pinned comment to add plugin). Thanks Philipp, you are awesome!
@@arminbuch9386 i just try to solve this issue and just you add `id 'kotlin-android-extensions'` in `plugins` tag in build.gradle inside app module, and sync project
@@andymukonkole I made the change but thought that the sync was automatic. after you do the change you have to click the elephant with a downward blue arrow to do that sync. That does the trick.
I’ve used and developed for both Android and iOS, and as a result, I’m not really biased. They are both good in their own ways. However, i will admit, because iOS has a proprietary language (Swift, SwiftUI or Objective-C and UIKit) it is SO much easier to develop an app, java and kotlin is very complex to me. Swift has a relatively straightforward syntax.
3 года назад
If I may… Thanks for the course, you really put a lot of work in this. But (sorry for that part) if I learned something in almost 40 years of coding it is that a beginner tutorial should always be done by a (almost) beginner! You clearly know what you are talking about but you lost almost everyone trying to explain too many different concepts while rushing some others. Android Studio is not a tool that can be mastered through a single course, especially if you don’t know Java, one of the hardest coding language still around (not JavaScript which is a breeze in comparison). An AS beginner course should probably be more focused on the interface, some basic code and a lot of visual stuff to set your interface up as well as a simple way to test your very basic app on a device, because that is the reward beginners are looking for. Anyway, as I said nice effort.
A word of advice for anyone trying to teach coding of ANY language. It's fair enough to do a video and try to explain the code. You should ALWAYS COMMENT your code regardless as when you go back to look at it, especially when learning the language or coding for the first time, having comments that will identify what the code is doing is a huge help. This is industry standards and should be used. There are several reasons, one is to remind you of the code (please do not think you will remember every line of code, where it points to in all the programs you work on, as you may well NOT work on EVERY part of a program), secondly, someone else having a look that is allowed to, to may be help with issues, or, come in fresh because you left for another job, as some examples, will need to be able to see what the code is for and what it is doing. You should get into the habit of commenting as you go OR, better still, comment that code before actually coding as this helps you plan your code better.
Also, don't make paragraphs, use short simple comments. Also, though not for this video but as a golden rule to know, when ever you create an application, database that may run alongside (full stack) or standalone, check if your country has automatic copyright. Designs may need to be registered or may not. This comes under Intellectual Property. IF you do not want someone using your code then DO NOT post it publicly. This video is for learning so that's fine, but, for real applications, check your country's copyright laws and if they apply automatically and at the top of each class, like with C# using the /// (comments vary so check) stick in there the copyright and who it belongs to and which country, whether it is automatic, date and that any copying, reuse or whatever is strictly by requesting permission to use the code. Keep the paper trail, this could prove vital if someone steals your code DO NOT share what you do not want people using. Boiler plate code? it's boiler plate and doesn't really refer to any program and boiler plate code is freely available. There is International Copyright acceptance and recognition between countries and anyone from another country using your code can be liable to a law suit if proven to be falsely claiming your code. Many countries have automatic copyright such as Barbados and the UK, not all but many do. Places like Github can be private or public. Check GPU Licence (general Public and can be used and modified) and EULA (End User Licence Agreement which is NOT public and can not be used and modified). Get in the habit as it could save you in lots of ways.
Ok thank you for helping but it was hard understanding what you were trying to say. I still went through the whole video but if you could explain more of the parts in depth, that would help my understanding by a mile. Thank you for the video!
As a Senior Flutter Developer, I fully endore this video. Amazing, clean and concise content. You have given me motivation to deep dive into Android and Kotlin more.
@@lardosian check "FilledStacks" RU-vid channel, as a Senior Flutter Developer, watching this just kept me thinking ".. yea I ain't coming back to this boys and girls 😅"
Great one .. keep doing this .. that's will make stronger and halp others to love more what they really wanted to love doing .. u just remind me of what a big part of me wanted to always been .. thank you for that ..
Love your teaching style. Easy to follow for someone like me who is such a newbie to coding. One question: I followed the tutorial and it came out fine except that the list wouldn't retain the entries. However, I did not do this as a standalone app - I added the todo list as an activity to an existing app I'm making. Would that be the reason the entries disappeared once I closed the activity and went to another page? Maybe there's a bit of extra code I'm needing? Thanks again for the tutorial. Really helpful for a 50+ lady like me who's such a rookie
My version of Android Studio produces a different default app with no LAYOUT folder/files and uses COMPOSABLE functions. So I'm totally baffled at the moment...
Hello thanks for this great tutorial :-) I was thinking what about making a part two, where we make it so the app can save data even after we close and reopen it ?
I just saw your video and I am amazed. You really explain everything and you really guide the user through every step. Good job, mate and thank you for the content !
had to give up near the end because apparently we have slightly different versions of the IDE and I couldn't solve a step... i wouldve liked a bit more explanation of each step tbh so i understood what was being done and what other options there were
Philipp, do you plan to make a video showing how to connect this todo list with a database so that items that are added to the list are retained when the app is closed and reopened?
Hi Philipp, thank you very much. This tutorial simplified my entry into the Android (Kotlin) world. You did it very well 👏 It seems to be very similar to the development of UIs with Qt (Designer), I didn't know it and this will make my life pretty much easier. Do you have a tutorial with a more complex Android app, I would buy and watch it.
@@yannickmussche5068 when creating project, create it using Empty Views Activity.... the Projects through Empty Activity are to be done with Jetpack Compose i guessssss
Thank you@@sapy4124 ! I was spinning my wheels like crazy trying to figure this out. Your response needs to be a pinned comment so people with the latest version of AS can figure this out.
@@yannickmussche5068 : maybe you found the solution already, but here goes anyway - you need to select 'Empty Views Activity' when creating a new project. Then you get the 'Activity_main.xml' tab from the start, and also the layout folder under res
After one hour of watching this video I have realized AS is already installed on my laptop so I can test it immediately instead of pure watching this :)
Hi Philipp.. I tried this code by following each steps and it's a success. How can I convert it to an App and how Can I load it to my android phone? Thanks for the videos, it's very useful.
Thank you very practical and simple, only the toogleTru it's a little bit complicated to understand and kotlin extensions it's deprecated, but it works just add in dependencies
@@Dinesh_Great yes, you need to go to your "build.gradle module: app" file where you will find a plugins block on top. In this plugins block, you simply paste this line and click on sync now: id 'kotlin-android-extensions'
omg, let me be honest. Classes seem to overcomplicate things that shouldn't be. I have been doing functional programming, my mind switched off after 40:00, Why do you need a separate class for every goddamn thing? It just complicates things. How do you learn what class inherits from what class? It is just a simple todo list for God's sake... I am just typing along without understanding shit. I worked with classes, but isn't this a bit overkill?
Because web development deals with a bunch of abstractions so you dont actually deal with many Computer Science concepts. Android development falls into the category of native development, which is far more complex than web development. Without native development, the components and tools that web development leverages wouldn't exist. In short, web development is very straightforward because most of the complexity has been handled by native developers
Philipp the way your explaining the cours is so fast and hard for beginners as me to fallow with you but good look I'm going to check your channel for more videos thanks
Sehr schön! Habe zwar etwas Ahnung von Kotlin, aber so gut wie keine Ahnung von Android... und teilweise habe ich nur Bahnhof verstanden xD... Muss wohl noch recherchieren. This is not for absolute beginners like me... xD
I wish they will eventually do all the heavy lifting with adding all these extra stuff in the layout building so we can just focus on code. Thats too much information to absorb just to build layout
