dlew/joda-time-android
dlew/joda-time-android has 2,614 GitHub stars and 184 forks. GitHot measured 0 stars in 24 hours. Last checked 2026-11-06 20:54 UTC. Last push 2026-10-29.
Joda-Time library with Android specialization
Measured star growth
- in 24h
- 0
- in 7 days
- Collecting history
- in 15 days
- Collecting history
- in 1 month
- Collecting history
Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.
README.md
Originaljoda-time-android
This library is a version of Joda-Time built with Android in mind.
Warning: joda-time-android is no longer a recommended solution for datetime handling on Android. Instead, I recommend using java.time.* package (w/ desugaring if necessary).
joda-time-android will continue to get tzdb updates for the foreseeable future to support any project that doesn't want to switch datetime handling.
Why Joda-Time?
Android has built-in date and time handling - why bother with a library? If you've worked with Java's Date and Calendar classes you can probably answer this question yourself, but if not, check out Joda-Time's list of benefits.
For Android developers Joda-Time solves one critical problem: stale timezone data. Built-in timezone data is only updated when the OS is updated, and we all know how often that happens. Countries modify their timezones all the time; being able to update your own tz data keeps your app up-to-date and accurate.
Why This Library?
I know what you are thinking: Joda-Time is a great library and it's just a single JAR, so why make things more complex by wrapping it in an Android library?
There is a particular problem with the JAR setup on Android: due to its usage of ClassLoader.getResourceAsStream(), it greatly inflates its memory footprint on apps. (For more details, see this blog post.) This library avoids the problem for Android by loading from resources instead of a JAR.
This library also has extra utilities designed for Android. For example, see DateUtils, a port of Android's DateUtils.
Usage
Add the following dependency to build.gradle:
dependencies {
implementation 'net.danlew:android.joda:2.15.1'
}
Multi-Process Apps
Due to using App Startup, joda-time-android will not automatically initialize in non-main processes.
If you would like to automatically run App Startup in other processes, add this to your manifest:
<provider
android:name="androidx.startup.InitializationProvider"
android:authorities="${applicationId}.androidx-startup"
android:exported="false"
android:process="[your-process-name-here]"
tools:node="merge" />
Alternatively, you can call AppInitializer directly to initialize just joda-time-android:
AppInitializer.getInstance(this).initializeComponent(JodaTimeInitializer::class.java)
Troubleshooting
Q: My build fails with an error about a duplicate file
Duplicate files copied in APK META-INF/LICENSE.txt
or
Duplicate files copied in APK META-INF/NOTICE.txt
A: We can safely exclude those files from our build. You need to specify these two excludes in your build.gradle file and you will be good to go:
android {
...
packagingOptions {
exclude 'META-INF/LICENSE.txt'
exclude 'META-INF/NOTICE.txt'
}
}
or
B: We can safely choose to add those files to our build. You need to specify these two merges in your build.gradle file and you will be good to go:
android {
...
packagingOptions {
merge '**/LICENSE.txt'
merge '**/NOTICE.txt'
}
}
Explore related projects
codecrafters-io/build-your-own-x
Master programming by recreating your favorite technologies from scratch.
560,404 starspublic-apis/public-apis
A collective list of free APIs
496,723 starsmorluto/rea
Reverse engineer anything with agents, from app behavior down to native binaries.
437,748 starsopenclaw/openclaw
The AI that really does things. Any OS. Any Platform. The lobster way. 🦞
394,058 stars