hi I am a newbie to android programming and I learnt many basic programs and now when I started studying some of the sample programs. I am getting confused about the flow of the program in the areas like one method calling another and so on,
Also I tried DEBUGGING but it didn't work fine as many of the apps need input from user for understanding the complete flow of the program
So is there a way such that newbies like me can first understand the flow of program then dig into the code written over there.
Look at the Android Activity Life cycle on the android developer site.
http://developer.android.com/guide/components/activities.html
Let me know if you have any questions,I will be happy to help where I can.
Related
I am a student working on a senior project. It will be a very simple android app to organize karaoke. We are using Flutter for the front-end work.
My education has been in Java, but this is my first time working with Dart/Flutter, let alone on a smartphone app. I have gone through Get Started (https://flutter.io/get-started/), as well as 2-3 step-by-step youtube tutorials that help you build very simple apps from scratch. These have been helpful, but I'm still having trouble wrapping my head around the organization of a Flutter app. All tutorials say "everything is a widget", as if that should make things simple. And maybe it does in the end. But I end up with so many widgets, and I am getting confused about what widget should be inside what other widget and why.
Take a look at this picture (in the middle of the picture I have the widget-tree on display). I have a stack, two columns, scaffold, container, etc. Do I really need all of those? Is this normal for a simple login page?
What helped you get a grip on Flutter? Or maybe it is app development, rather, that I am having trouble understanding. Regardless, I am getting a bit discouraged. Any advice? Maybe there is a particular tutorial that helped you a lot?
Thank you for any help.
I like to learn by downloading and running examples from the developers (like these ones in their GitHub repo).
One thing I struggled with at first too from the whole "everything is a widget" idea was figuring out how to handle state / data changes appropriately. If you're struggling with that, this Google I/O video does a great job showing how you can better architect an app in regard to handling state in a reactive way. A bit more advanced, but from beginning to end they go from their opinion on the worst way to handle state changes to their recommended way(s).
I am looking to make a messenging application for both Windows and Android over Wi-Fi. I have looked around for answers and have come back with a loads of articles that mention Client-Server applications, which is what I want to be using, but they do not mention clearly how everything works or where to start. Could anyone point me in the right direction?
Extra Information:
If possible c# for the server-side as Im more skilled in c# than other languages although I don't mind learning a new one.
Articles I've Read:
http://csharp.net-informations.com/communications/csharp-socket-programming.htm
http://www.dreamincode.net/forums/topic/33396-basic-clientserver-chat-application-in-c%23/
I am about to decide which way to push our smartphone development.
I have read numerous articles about these technologies. I have also created test apps, but wanted to be 100% sure that I get this right.
I am not able to create EXACTLY the same look and feel like native app in PhoneGap because it runs in WebView Controler. And the webish look and feel is as far as I will get with this tech. correct?
(In the example app I have created with PG, the look might be similar, but there is a delay when i click on buttons and the animation is not so fluent as in native apps)
Latest Titanium seems to have changed its approach to WebView, to remedy that lack of look and feel of native apps. My question is (I havent tested this myself). Can I create EXACTLY the same look and feel of an native app with Titanium?
EXACTLY is the key word. I mean can a person tell a difference if app was created with Titanium? because I can definitely tell that app was created with PG.
Final goal is the UX, ppl sense this things, and on smartphones anything that is webish and is suppose to be appish is a bad UX i believe.
Thanks
Compared to PG Titanium is more Native like UI experience but it's kinda problematic for Android.Since it's originally intended for IOS.
Titanium for Android is pretty buggy and can mess you up and the thing that you have to come up with workarounds and if you cant find any then you are stuck.
But if you are okay with that and i can easily advise that Titanium is way to go though it's nearly native (not exactly) which close to exactly.I dont think an average user would understand Titanium .
2) yes, since titanium uses the original UI. your javascript code is wrapped to native Objective c code that creates native elements. only constraint is that your are not as flexible as with real native code written by yourself. but you can write native modules and add them to your projekt. so you're able to expand your project with custom UI too.
I'm planning to develop a simple tic-tac-toe 3D game for android as a starting point (practical task to learn and do something useful), but devguid seems to be more of a reference than something with what I can get my hands on particular task. Can someone advice what should be investigated? (or maybe I'm searching for it incorrectly)
EDIT: I'm also considering other options on learning android development. (Though, the "practice while learning" approach is preferred).
EDIT:
My purpose: learn how to develop apps for android && create an app, which is fun and can be placed on android market
My initial "data": strong java + java ee, basic C/C++, willing to learn
Means to achieve purpose: devguide is more of a reference, and I need a solid start with lots of explanations. Need an advice here.
You see, to my mind there is no sense to read books and so on. First reading starting manuals from Google should definately help. When you are done with them you should jump into development. Of course, you will have a lot of questions, however there are lots of great manuals and tutorials all over the internet, so you will rarely have difficulties. If you even though have them, come here and we'll help =) Check out my devBlog
I did a simple tic tac toe for my first Android application and I was able to create a working game quite quickly using a table of image views. You just need to add clickHandler events onto the image views so they change image on click, and write a function checking whether the game is won after the click.
Try out several tutorials here, especially testing ones. Get your hands on Pro Android Games with reading devguide when some part of android development is unknown.
This will result in a rapid development (with a zero level starting point) and small learning curve of basic + in deep android development.
Recently I was asked if I could help someone to get quick-started to android programming.
What would you suggest to tell this person?
Would you explain everything by hand or just refer to external links?
Which ressources would you recommend?
This whole issue should not take too much time...assuming 2-3 hours
Once my access to this issue was "Professional android application development".
Java basics are already preconditioned, so there's no need to explain ANYTHING.
For avoiding any misconceptions: This shall be just a quick start, no reference or something like this, so I just need some keywords and a hint how deeply go through it.
In my opinion, everything you really need is here: http://developer.android.com/index.html
All the downloads are easily accessible, the API reference is there, and the Dev guide is pretty well done.
This page has a getting started "Hello World" type tutorial that should work for your quick start: http://developer.android.com/guide/tutorials/hello-world.html
As far as your 2-3 hours goes. I would walk them through the hello world tutorial first as it gives a quick and dirty overview of the most important basics such as getting a project created and a virtual device up and running to test with. It will also start getting into installing and debugging.
That shouldn't take up all of your time so you may want to go into some basics of building a UI and concepts like Activities and Intents. Pointing out the API reference would be great at this point as well. I suspect that most of that 2-3 hours would be up if you get into any sort of detail on these.
Well you already mentioned a book in your question, so I would like to throw out http://commonsware.com/Android/ .
I've been working on an Android project for school, and I still have A LOT to learn, I dont think you can cover much in 2-3 hours. But anyway, with the above book, you can find an example that is similar to what your trying to accomplish(or go over), then look through the source code and what-not.
Aside from the Android Dev. website, the $40 collection of ebooks is the single best resource I have found to date other than Google searched or examples specific to my project.
Sorry if this doesnt really help your cause, but I figured it was worth pointing out.