Which Android development blog has the most walkthroughs and tutorials? [closed] - android

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I need to work on my Android development skills. Which blog has the freshest and most walkthroughs, code samples, and tutorials?

the freshest and most walkthroughs, code samples, and tutorials?
Unfortunately I don't think this is the best approch. Many of these tutorials are a year+ old (when Android was still in its alpha release); a lot has changed in terms of the API and UI conventions.
Included API Samples
I recommend being familiar with 1)simply creating a project and then 2)reviewing all the API samples included in your Android dev install. These samples should be in the \samples\ApiDemos\src\com\example\android\apis folder of your Android install path.
Android Tutorials
About 6 months ago I presented an Android overview at NYU's ITP with a simple hello world tutorial. It details how to get Eclipse and your first app up and running. It can be found here:
http://perkmobile.com/tutorial_helloworld/Perk%20Mobile%20Android%20Tutorial.html
Also, we provided an mapping tutorial that demonstrates how to use web services in conjunction with Androids mapping control. Most importantly it shows how to safely makes use of background threads for managing HTTP requests.
http://perkmobile.com/itp.html

You might want to look at the list of blogs at planetandroid.org the list is on the right side.

Well at least the "official" Android development blog contains pretty recent entries at http://android-developers.blogspot.com/

Tutorial series for 2D and 3D on droidnova.com - Android Development

If you are looking for a comprehensive introductory tutorial for Android development, please check out my own (Game of Life) tutorial: http://www.quesucede.com/page/show/id/conway_game_of_life_android.
Areas covered include (but not limited to): implementing a custom (orthogonal grid) component, a so-called 'game loop,' and the implementation of and the subsequent interaction with a preferences activity.

Related

Should I learn Unity C# for PC before learning Unity for Android? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
I want to start learning Unity, I'm a web developer and I have a decent level in C# but I've never touched Unity before.
I mainly want to create games for Android (maybe iOS in the future), there are many courses on the internet but I'm wodering if I need to have a good understanding of Unity PC/Mac.. before trying to learn Unity for Android.
I found this course : https://www.udemy.com/course/unitycourse/, It seems like a it's a complete and detailed one, but it has nothing to do with Android. Should I learn something like this first?
I'll appreciate any advices, thank you.
As an android developer that made a few games with unity, I think that if your end goal is to develop for android so just start with that..
I developed several apps(games) for android and I didn't had any problem with it and I didn't even know C# before.
Besides, you will get a better idea about how to make an optimized app that can work well on Android.
You can find some great Videos on youtube, for example this channel
Do a quick project on the desktop first.
The setup required to build for android devices will be an extra hurdle to get over, so I would recommend starting with a project that you can develop directly on the desktop, if the primary goal is just learning.
Besides the small amount of extra work it takes setting up Unity3d to build for Android, it will also be a slower to build and run the project on a smartphone than just running it directly on a desktop. And there will always be a lot of trial and error when you are still learning.
And if you think ahead, it might be no problem porting your desktop-project to mobile after a while. Touch can be pretty similar to a mouse, and Unity3d won't care about the difference in many cases.

Advice for moving from WP8/WPF to android development [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I'm a WPF and WP8 developer and I'm planning to develop all my current apps for android too. I did some research and read a little about android development. From what I've read, Android's XML is terrible compared to XAML. The tags are long and terrible (For example, why couldn't they just have Width instead of android:layout_width ?) And the most annoying part was that there is no equivalent for data binding.
So, I looked into alternatives and came across Xamarin, which seems a better. But I have a few questions I was hoping someone would help me with.
My biggest question is should I go for Xamarin or go ahead making native android apps in java? Is there any disadvantage on using Xamarin? Because there is a good thing about it that I can reuse most of my code..
Is there data binding like functionality in it?
Does Xamarin support all features that a native app would? Will I be able to get Material UI design templates in it?
Also, if you have any other advice or suggestions do let me know.. Thanks
My suggestion would be.
1)
Take it easy. Android development is not that bad.
It is true, you do not have data binding facilities as you have in WP but that is not end of the world.
Android xml is simple and it beautifully solves the issue of different screen sizes and types.
You have to write more code in android than in WP. WP came after android which allowed Microsoft to come up with better development patterns for rapid development.
2)
Big no for Xamarin. Xamarin reduces your options because it relays on android library wrappers in c#. Only benefit of Xamarin is to have common business logic. that is normally 5% percent of any project. In most cases you would find yourself in very tight situation; for instance, if there is any good 3rd party android library that you want to use in your project then you have to wait Xamarin wrapper for this library in order to use it.
3) Not always, you would find restrictions

Multilingual Android Sdk Documentation [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
We have a social responsibility project aiming encourage young people to learn mobile application development. The main problem we face mostly is language. Most of the young people in our country don't have sufficient english knowledge to be able to search or learn something in english. That's why our one of the biggest difference from the world wide tutorial/learning sites is being in native language.
As a supporter of the project in the technical side, we answer questions, write blog posts and try to help people learn mobile application development in their native language. One of the problems i face with while helping people is the inability of providing official references(in native language) about the responses we gave. This problem pushed me thinking about translating whole android sdk documentation to our native language :) I know it's a huge job, we may try to crowd-sourcing it i dont know but the thing i want to ask here is just suggestions about implementation of such a project.
What kind of technology would you use, how would it be possible to stay synch with the recent versions of the sdk. Do you think the current android sdk documentation pages auto-generated completely? Is it just java-doc? How to support multi-languages with java-doc? Or with any other way?
I hope questions will not be closed being unrelated, it is a completely technical question.
Thanks everyone
Interesting question!
I guess not only do you want the Java documentation, but also the tutorials and everything that is provided by developers.android.com.
I think you should ask Googe / the developers of Android directly for support, e.g. here. I'm pretty sure they like the idea and support you with that by giving you access to some feed that keeps the tutorials up-to-date.
An independent solution would be to implement a crawler for developers.android.com and track the changes yourself. Yet I don't know how much effort you can/want to spend on that.
For the crowdsourcing: I did a project once for crowdsourced writing error correction, where we used Amazon Mechanical Turk. It is used for translation too. It is quite easy to build your custom tasks for the crowd and to automate the whole process. They provide a Java API, for example. It costs some money, but is quite cheap in comparison to professional translators.
Just some suggestions...

Where can I find willing open source Android contributers [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 8 years ago.
Improve this question
I am writing an application which I hope to build a client for in Android.
However, I am fairly inexperienced in Android development and am looking for droid devs who would be willing to contribute to my open source client.
Where can I find such people? I dont care where they are, just as long as they have a strong grasp on the english language.
*edit: to clarify - I am not trying to recruit people through stackoverflow, merely where such people would register as willing contributors looking for a project, so I can look through their profiles and get in contact with them.
I would post you project on an open source repository website like GitHub or Google Code. And start making commits and post information on the app. Most open source projects start with a few devs and the community kicks in once you have a decent user base. I feel like the best way to recruit people to to put your project out there and show people that it has potential. Then people will want to contribute to it.
Maybe you are looking for Android contributors group.

Open-sourcing a mobile app [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I'm considering making an existing mobile app into an open-source project. It has an Android and iPhone version.
While I have used open-source projects and submitted feature requests and bug reports, I have never created an open-source project nor contributed with a patch to an existing one.
What are the top things that I should take into account before opening the source of my project? What specific steps do you recommend taking for open-sourcing a mobile app?
You are lucky as when I started to run open source projects I did not realize this great book exists,
http://producingoss.com/
It provides general tips in almost all aspects of running an open source project, and you can add your own for mobile world.
You can publish you code on googleCode, SourceForge or Github, use all the power of theses websites (documentation, notes etc..) will help contributors.
And don't forget to comment your code ;-)
GoogleCode is a good place to upload your project.
There you will have an issue tracker and a wiki to write about it.
For a truely awesome OSS application I would suggest that you use git. Free hosting for git is provided by github. A good starting point for using git is http://learn.github.com/
As far as FOSS development is concerned, its not very different from usual development. But here you will have to don different roles like product manager, developer and tester too.
Other things that you need to take care of.
Since you are the initiator of it, you need to take control of its development.
Your code should be easy to be understood by others. Documentation is of utmost importance for other developers to start off.
Dont be offended if someone creates a fork of your project. Know to protect yourself by putting appropriate license, like, GPLV3 or any other that you find appropriate.

Categories

Resources