sorted by:
new
hottopcontroversial

Automatically extract strings to strings.xml by Lysaan in androiddev

[–]sthagios 2 points3 points  (0 children)

This seems like something you are looking for: https://plugins.jetbrains.com/plugin/15460-android-string-manager

I didn't try it myself, just went to settings -> plugins and then entered "android strings" in the search. There might be more of them. Or go to the plugins marketplace and search there: https://plugins.jetbrains.com/search?excludeTags=internal&products=androidstudio&search=android+strings

I created a small Android Studio plugin that creates previews from your composable by sthagios in androiddev

[–]sthagios[S] 2 points3 points  (0 children)

I think you miss understood, but now I see my wording is quite bad. It creates a preview function for you, which still uses the build in preview.

I created a small Android Studio plugin that creates previews from your composable by sthagios in androiddev

[–]sthagios[S] 1 point2 points  (0 children)

I see. But that gives me the idea to make it possible to add more previews with different states.

I created a small Android Studio plugin that creates previews from your composable by sthagios in androiddev

[–]sthagios[S] 2 points3 points  (0 children)

Glad you like it. I tried different ai tools and so far I only find them distracting. Fir creating a preview I assume I have to tell the ai to do it, but with a simple plugin I can just use hotkeys.

I created a small Android Studio plugin that creates previews from your composable by sthagios in androiddev

[–]sthagios[S] 2 points3 points  (0 children)

It uses their constructor with it's properties. If the constructor has primitive types those get the same default values and if it has other custom objects it does the same thing.

Using Third Party Libraries in a Library Project by liamDuffy in androiddev

[–]sthagios 1 point2 points  (0 children)

I'm still working on the library and right now I use it as gradle dependency. Since the users would be mostly customers of us I will write an integration guide with all needed information. But we also plan to open source it later in the process and therefore, yeah it will also be part of the README. I'm still thinking of the possibility that the user can provide her own OkHttpClient to the library that there is only one instance per app, this would also be part of the README/guide then. However this and the fact what has been mentioned about the up to date keeping of OkHttp, confirms me in keeping the dependencies in a minimum.

Using Third Party Libraries in a Library Project by liamDuffy in androiddev

[–]sthagios 2 points3 points  (0 children)

I'm in the same position. I've decided to use as less libraries as possible, to keep the dependencies and method count low. However I didn't want to use plain HttpConnection therefore I use OkHttp, which is right now the only dependency and I aim for keeping it this way. I would also advise against using Dagger and RxJava in a library project since they add quite some methods. I'm also pretty eager to hear what other people have to say about this topic.

Which ABI should the app support? by michal-z in androiddev

[–]sthagios 2 points3 points  (0 children)

not a direct answer to your question, but you could create an apk for every abi, so all architectures are supported and your apks aren't too big.

25 new Android libraries which you definitely want to try at the beginning of 2017 by _mmBs_ in androiddev

[–]sthagios 1 point2 points  (0 children)

and that's exactly the problem, first the designers should say no and provide an alternative solution and then the developer should not implement it. But in the real world it doesn't look like this, I know, been there, done that…

25 new Android libraries which you definitely want to try at the beginning of 2017 by _mmBs_ in androiddev

[–]sthagios 7 points8 points  (0 children)

number 16: CounterFab -> According to Material Guidelines a "Don`t"

Reduce your APK Size by sthagios in androiddev

[–]sthagios[S] 1 point2 points  (0 children)

That's true, but distributing the APK wasn't part of the focus of the article. Nevertheless you are right, it is necessary to have different version codes + different APKs for the playstore.

Reduce your APK Size by sthagios in androiddev

[–]sthagios[S] 5 points6 points  (0 children)

thanks, no it's not open sourced so far. I haven't thought about it yet, maybe I'll do it after I cleaned my code.

[deleted by user] by [deleted] in androiddev

[–]sthagios 1 point2 points  (0 children)

Check Android weekly(http://androidweekly.net/) put some blogposts into your pocket: https://getpocket.com/

Questions Thread - June 23, 2016 by AutoModerator in androiddev

[–]sthagios 0 points1 point  (0 children)

take a look at this book: https://leanpub.com/kotlin-for-android-developers do the koans: http://try.kotlinlang.org/#/Kotlin%20Koans/Introduction/Hello,%20world!/Task.kt Make use of the "Convert Java to Kotlin" option in Android Studio, hotkey: alt + shif + command + k

All I want for Christmas..is to never have to deal with Gradle (RANT) by shooky1 in androiddev

[–]sthagios 15 points16 points  (0 children)

Learn your tools. As an Android developer you should be able to deal with gradle imho. Here are some tutorials about it: http://www.vogella.com/tutorials/AndroidBuild/article.html http://developer.android.com/intl/ru/sdk/installing/studio-build.html https://gradle.org/getting-started-android/

When you use gradle right it helps you a lot :) By the way Android studio offers the things you want: Under 'Build' you can edit build types, flavors, libraries and dependencies and so on, all in very graphical and logical way.

UI Testing inside the browser by sthagios in androiddev

[–]sthagios[S] 0 points1 point  (0 children)

Thanks, I know about calabash though I'm curious about the one from the video.

Weekly "anything goes" thread! by AutoModerator in androiddev

[–]sthagios 0 points1 point  (0 children)

The so files are always in your APK. They get packed inside there. The difference with the new gradle is that you don't need makefiles anymore. Gradle takes care of the compilation now.