If you maintain shared libraries across multiple Android or Kotlin Multiplatform projects, you’ve probably considered publishing them to a Maven repository. Maven Central works, but the publishing process is heavy — GPG signing, Sonatype staging, approval delays. For private or small-scale libraries, that’s overkill. If you already self-host a Git server like Gitea or Gogs, you can use it as a Maven repository with zero additional infrastructure.
Umami is a great privacy-focused, self-hosted alternative to Google Analytics. But its documentation assumes you’re tracking a website. If you want to use it in a mobile app, the docs point you toward embedding a WebView — which is clunky, adds overhead, and feels wrong for native apps. There’s a better way: hit the Umami API directly.
FreqDroid 1.2 is out with two notification upgrades: a new in-app notification history screen and support for rich exit notifications via FreqTrade’s strategy callback — giving you Telegram-style trade alerts without Telegram.
Introduction
In the ever-evolving world of mobile app development, choosing the right cross-platform framework can be a game-changer for businesses and developers alike. Two prominent contenders in this space are React Native and Kotlin Multiplatform (KMP). Both offer unique approaches to the challenge of writing code once and deploying it across multiple platforms. This article will dive deep into the strengths and considerations of each, helping you make an informed decision for your next project.
Model-View-Intent (MVI) is a powerful architectural pattern for building user interfaces, especially in Android development. In this post, we’ll explore a helper class that simplifies the implementation of MVI, making it easier to manage state, handle user intents, and emit actions in your application.