You're looking at Less Wrong's discussion board. This includes all posts, including those that haven't been promoted to the front page yet. For more information, see About Less Wrong.

Elo comments on Open Thread, Jun. 15 - Jun. 21, 2015 - Less Wrong Discussion

5 Post author: Gondolinian 15 June 2015 12:02AM

You are viewing a comment permalink. View the original post to see all comments and the full post content.

Comments (302)

You are viewing a single comment's thread. Show more comments above.

Comment author: Elo 18 June 2015 02:42:19AM 0 points [-]

I too am confused about my goal.

Original goal: make an android app that does something (specific and not particularly important right now).

My path: try to use android studio via developer.android training (as linked in the first comment). Get lost. Try to work out what was going on. Discover what OOP actually is. Read more and more. Roughly get to where I am now.

Important question: Is there are better/smarter/faster/easier way to be making an app? I figured android studio would be the most easy to use (where I was previously not sure how to get an app onto the phone) because its built to go with android devices.

Comment author: Viliam 18 June 2015 02:02:40PM *  1 point [-]

Just make sure you don't try going too meta too soon, otherwise you may lose touch with reality.

1) The "hello world" app you made -- did you have anyone review your code? Maybe it contains obvious errors you didn't notice. Maybe learning about them could be very beneficial in long term. Having an improvement shown in a program you already spent a lot of time thinking about could be better (more motivating, easier to remember) than reading about a similar technique in a book illustrated with a fictional example.

2) Every time you learn something new -- do you also make another "hello world" app to test this new knowledge? Otherwise you may get a fake understanding. Also, if you learn about cool new techniques, but never use them, you may not understand the trade-offs. By making sample applications you test your new models against the reality.

I figured android studio would be the most easy to use (where I was previously not sure how to get an app onto the phone) because its built to go with android devices.

I agree.

Unless you want to make a game, in which case Unity is probably a better option. It is not Android-specific, but it can compile to Android platform.

EDIT: Feel free to ask me specific things about Java or Android.

Comment author: Elo 19 June 2015 12:55:37AM 0 points [-]

Thanks!

  1. it took hours to figure out how to correctly install Android Studio and get it to compile. Including completely starting again; installing extra packages and accepting that some errors will exist.

eventually most of the hello world app was a sample program; so I didn't really write it; just worked out how each part went together and how the files were stored in the weird app-code-files folders.

  1. I will be making test programs along the way hopefully. Thanks

Not a game; shouldn't have to worry about it.

Will ask if I need. Thanks!

Comment author: Lumifer 18 June 2015 02:52:11AM 0 points [-]

Sorry, I haven't played in the Android world so I'm useless there.

As a general piece of advice about an easier way of making an app -- find an open-source app that does something in the same ballpark as what you want your app to do, understand how the relevant parts of it work, then modify them to make the app do your stuff.

Comment author: Elo 18 June 2015 02:55:17AM *  0 points [-]

I tried looking at a bit of github; but found I lacked fundamentals of OOP to make any sense of what I was looking at. I will see if my final construction is within my reach (after some more reading); if not - I will head back to the gits and fork someone else's code.

Also thanks for the help!