scala-android

sbt-android

Java2014–2019

scala-android / sbt-android

sbt-android

An easy-to-use sbt plugin for working with all Android projects

Mobile & Desktop

Explore on GitHub Read Hacker News discussions

6Distinct people

6Mentions

0Explicit recommenders

733GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

An easy-to-use sbt plugin for working with all Android projects

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year6 dated mentions

Observed mentions: 2014-06-04 04:00:08 UTC to 2019-12-22 19:52:09 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
2014	2014-01-01 00:00:00 UTC	2015-01-01 00:00:00 UTC	2	2
2015	2015-01-01 00:00:00 UTC	2016-01-01 00:00:00 UTC	0	0
2016	2016-01-01 00:00:00 UTC	2017-01-01 00:00:00 UTC	2	2
2017	2017-01-01 00:00:00 UTC	2018-01-01 00:00:00 UTC	1	1
2018	2018-01-01 00:00:00 UTC	2019-01-01 00:00:00 UTC	0	0
2019	2019-01-01 00:00:00 UTC	2020-01-01 00:00:00 UTC	1	1

What Hacker News says

6 sources

sideeffffect·Dec 22, 2019

> not sure there are any real blockers for Scala on Android anymore. I imagine it's mostly a resource problem now not really, it's still the problem Android being Java < 8, and Scala on Java 8 features. https://github.com/scala-android/sbt-android/issues/334#issu...

In The Road to Scala 3

bad_user·Jul 28, 2017

Google is bringing Java 8 support, and from what I understood from one of their engineers, they are working on supporting invokeDynamic as well, so we might get the whole package: https://android-developers.googleblog.com/2017/03/future-of-... Scala 2.12 has moved to Java 8 indeed, however this means modern features that are used for encoding Scala: invokeDynamic and default interface methods. These should make Scala compiled code faster and more stable in regards to backwards compatibility. Both Java 6 and 7 have need EOLed. We cannot stand still because of Android's shitty support. Google has effectively fractured the ecosystem, pulling off what Microsoft couldn't do with J#, and they got away with it. I actually think that they preferred to announce Kotlin as being a first class citizen as a marketing trick in order to offset the lack

Read the rest

of support for Java 8. Even so, Scala does in fact have great Android support: 1. Scala 2.11 will remain supported for some time, language-level features have already been backported from 2.12 and Typelevel.org also has a commitment to support it even further 2. We have great integration with the tool chain, see https://github.com/scala-android/sbt-android 3. For a pretty cool open source project made with Scala, that uses functional programming libraries like Cats and Monix, see: http://www.9cards.io So if you think about it, given all the other tooling available, compared with other languages Scala actually has stellar support, along with actual projects ;-)

In Scala 2.12.3 Released

premium-concern·Oct 26, 2016

Method count forces multidex insanely early into development and for people who want the best UX that alone is a show stopper. That's a complete non-problem. Minimal overhead of Scala is 30kB (see http://scala-android.org/) and it doesn't grow much larger even after dragging in the collections API. Every single of Google's Android compat shims is way larger. Here is a data point from a small example app written in multiple languages: https://github.com/SidneyXu/AndroidDemoIn4Languages If you need multidex (you probably don't), it's a single setting away. Very slow compiles (contrary to what you claim). After saving in my IDE, the plugin has incrementally compiled, ProGuarded, dexed and deployed the app to my phone before I can even grab it. That's pretty fast in my book. testQuick is also amazing as it runs only the tests that h

Read the rest

ave failed, haven't run before or depended on code you just changed: http://www.scala-sbt.org/0.12.4/docs/Detailed-Topics/Testing... Language style encourages constructs that cause GC spikes, closures are not low overhead Google has official recommendations on what to avoid in Java. You can follow the same rules and be fine. Closures have the same overhead as if they were written in Java. SDK dependencies automatically meaning what? The thing AS does for imports from AppCompat and co? No. SDKs (and NDKs) are treated like every other dependency, which means the plugin resolves, downloads, installs and manages them automatically (see https://github.com/scala-android/sbt-android#usage). This is especially useful if you work for multiple clients that have different SDK requirements. No need to write wrappers around Gradle scripts to run https://developer.android.com/studio/intro/update.html. No need for setup instructions if you hand the project to a colleague. Better instant run? Protify existed before Google released Instant Run and is therefore more stable and mature: https://www.youtube.com/watch?v=LJLLyua0bYA It's so seamless that people use it for live-coding Android apps. ... And then you have goodies like typed resources: http://scala-android.org/tips_and_tricks-typed_resources/ Or the automated Gradle config import which means you don't need to do configure anything except adding the plugin: https://github.com/scala-android/sbt-android/blob/master/GRA...

In Server APIs Project

airless_cotton·Apr 29, 2016

As far as I know, sbt-android just recently got even more support/features for NDK (on top of the existing support): The plugin can now manage and auto-install SDKs, tools, support repos and NDKs, so no messing around with Google's `android` tool anymore! Maybe this is of use to you. https://github.com/scala-android/sbt-android/commit/7b32e55f... https://github.com/scala-android/sbt-android/commit/53b855de...

In Android Studio 2.0 Is Google’s New, Improved Development Suite

eeperson·Sep 1, 2014

Have you looked at the usage guides for the various plugins [1][2]? [1] https://github.com/jberkel/android-plugin/wiki/getting-start... [2] https://github.com/pfn/android-sdk-plugin#usage

In Kotlin, the Swift of Android

nilium·Jun 4, 2014

The only thing I can imagine would be relevant is that I'm using pfn's android-sdk-plugin.[1] I also have a sort of generic build.scala file I tend to reuse for Android projects (it's based partly on Ascension's, but has been tweaked a bit), which may also be useful.[2] I leave most of the proguard configuration up to pfn's sbt plugin since it does an acceptable job, but your mileage may vary. [1]: https://github.com/pfn/android-sdk-plugin/ [2]: https://gist.github.com/nilium/db5bfac2174370ebdd97

In Show HN: I built an Android live wallpaper with Scala – now it's free