51–60 of 81 posts
Earlier quoted context omitted.
IB is perfectly fine for most apps. When you feel constricted it is easy enough to accomplish what you want in code.
What happens if you try to open an iPhone app on an iPad? What happens if you try to open an Android phone app on an Android tablet? That's the difference between IB and Android's layout system.
[0]https://www.raywenderlich.com/115440/auto-layout-tutorial-in...
You need a pretty powerful machine to run Android Studio. It lags when I run it on my laptop with an i5 and 6 GB ram. I wonder if upgrading to a SSD will increase performance.
That's an extreme case though, most projects can be worked on with reasonable machines. An SSD really helps though
Earlier quoted context omitted.
Just be aware that C and C++ are really meant for programming games, bringing code from other platforms or improve performance. Trying to write an app that isn't a game will make you enjoy the pleasures of JNI calls, given the APIs exposed to the NDK.
I know, since my first attempt was in Java to create a simple app. I know the NDK can be used to create OpenGLES guis, and access the sensors, but for a traditional app it's a lot of work. Syntax is a subjective thing; I just don't like Java. I was hoping Google was going to come up with something (other than Go), for Android. I have tried a lot of the work arounds, and simply put, Java is the way to do Android right…
Java is and will keep being the only main language on Android, with a little help from C++ when needed.
https://www.reddit.com/r/androiddev/comments/4tm8i6/were_on_...
I am on a similar route, but I do like Java, what I dislike is their fork that prevents me to fully use Java™.
Earlier quoted context omitted.
Have you tried Kotlin ? It does a really good job at fixing java's issues and since it outputs bytecode, you can write entire Android apps with it without writing a single line of java.
Not in a year, but it wasn't different enough to me - less verbose, but the same when I long for a Lisp or ML or Haskell for Android! Scala was a thought. And I am now looking at F# again with the recent OS works by MS and the Xamarin situation. As I wrote downstream, I just need to commit to Java (or Kotlin!) I think!
Earlier quoted context omitted.
IB is perfectly fine for most apps. When you feel constricted it is easy enough to accomplish what you want in code.
What happens if you try to open an iPhone app on an iPad? What happens if you try to open an Android phone app on an Android tablet? That's the difference between IB and Android's layout system.
I tried many times to get into android development but everytime I get put off by the complexity of the api. The amount of digging in documentation you need to do in order to implement the simplest functionality scares me. Is anyone else feeling the same way? And does anyone know if it gets better with time or is it a constant struggle?
Some things are much more sane and well thought out than iOS. Styling and layouts, for example, are so much better than Interface Builder, which is pretty much just a toy for demos. Other things like the way events are handled and some of the native widgets are clunky. Some of us are fed up enough with all the incidental complexity Apple puts in your way every day as a developer (provisioning, in particular), that we…
Earlier quoted context omitted.
Some things are much more sane and well thought out than iOS. Styling and layouts, for example, are so much better than Interface Builder, which is pretty much just a toy for demos. Other things like the way events are handled and some of the native widgets are clunky. Some of us are fed up enough with all the incidental complexity Apple puts in your way every day as a developer (provisioning, in particular), that we…
IB is perfectly fine for most apps. When you feel constricted it is easy enough to accomplish what you want in code.
- No way to define reusable styles.
- No way to compose layouts out of other layouts.
- Trait classes are way too coarse to be useful.
- Versioning of Storyboards is a nightmare.
- Anything beyond trivial auto layout editing is useless.
- Segues force you into stringly-typed APIs.
- @IBDesignable is still super buggy.
I've dabbled in Android dev, but have always lagged due to not really liking Java. Android Studio was a pleasant experience for me when I tried it this year, and now that C/C++ NDK support is better in this release I am going to give it another go. I almost feel like I should just go completely Android given the numbers of devices out there is overwhelming compared with Windows/iOS/OS X combined. I will keep up with…
Earlier quoted context omitted.
Not in a year, but it wasn't different enough to me - less verbose, but the same when I long for a Lisp or ML or Haskell for Android! Scala was a thought. And I am now looking at F# again with the recent OS works by MS and the Xamarin situation. As I wrote downstream, I just need to commit to Java (or Kotlin!) I think!
Check Xamarin documentation they have some Android F# samples.
I am thinking more and more against my wish, that biting the bullet and just going Java all the way is the key. Kotlin, Xtend, you still have to read Android SDK code in Java, correct?
In terms of books, a friend bought me "Android 6 for Programmers: An App-Driven Approach (3rd Edition) (Deitel Developer Series)" to get me off the fence. I am going to work through it as much as I can to give Java a fair shake. I used to program in Java 5 for little side projects, but never mobile except for demo or tutorial apps years later.
Is this a good Android/Java book, or should I stay on board with my interests and do an Android Game or Android AI book slant?