Open-source issues tracker and performance stats collector enhances app quality and stability. Customizable engine collects data, tracks issues, and supports multiple platforms for analysis.
v1.0.4
This project, based on Java and the Spring Boot framework, is an open source self-hosted issues tracker and performance stats collector about Compose Multiplatform applications
Improve the quality and stability of your apps with Ametista!
This repository contains the engine of Ametista, so if you want to customize you can fork it and work on it, if there are any errors, fixes to do or some idea to upgrade this project, please open a ticket or contact us to talk about, thanks and good use!
It is the core component of Ametista. It collects performance data and tracks issues to send to your backend instance for analysis.
This project will be constantly developed to reach different platforms to work on, following the platforms releases steps:
When an error occurs during the runtime of your application, it will be automatically caught and sent to your server instance for tracking. It keeps tracks also of the different versions of the application
[versions]
ametista-engine = "1.0.4"
[libraries]
ametista-engine = { module = "io.github.n7ghtm4r3:Ametista-Engine", version.ref = "ametista-engine" }
Add the JitPack repository to your build file
Add it in your root build.gradle at the end of repositories
To share the sensitive configuration data with the engine and avoiding adding to the external configuration file it is recommended to use the gradle-buildconfig-plugin to generate at runtime the sensitive information to include in the binaries. This is a similar approach used on Android with the BuildConfigField.
build.gradle.kts of the composeApp module:
plugins {
id("com.github.gmazzo.buildconfig") version "5.5.1"
}
gradle.properties file:[!CAUTION]
#Ametista
host=your_host_address
server_secret=your_server_secret
application_id=your_application_id
#whether bypass the SSL certificates validation, this for example when is a self-signed the certificate USE WITH CAUTION
bypass_ssl_validation=true (if not specified false as default)
build.gradle.kts file):
buildConfig {
className("AmetistaConfig") // suggested class name
packageName("com.your.package") // your current application package
buildConfigField<String>(
name = "HOST",
value = project.findProperty("host").toString()
)
buildConfigField<String?>(
name = "SERVER_SECRET",
value = project.findProperty("server_secret").toString()
)
buildConfigField<String?>(
name = "APPLICATION_IDENTIFIER",
value = project.findProperty("application_id").toString()
)
buildConfigField<Boolean>(
name = "BYPASS_SSL_VALIDATION",
value = project.findProperty("bypass_ssl_validation").toString().toBoolean()
)
}
[!CAUTION]
To send the issues and the performance analytics to your backend you have to create the related "ametista.config" configuration file:
The first step to start the engine is intake it in each main of your application targets platform
AndroidManifest.xml
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android">
<!-- ADD THIS PERMISSION -->
<uses-permission android:name="android.permission.INTERNET"/>
<application>
...
</application>
class MainActivity : ComponentActivity() {
override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
// invoke it before the App() invocation
AmetistaEngine.intake()
setContent {
App()
}
}
}
Intake the engine in your MainViewController.kt script file
fun MainViewController() {
// invoke it before the App() invocation
AmetistaEngine.intake()
ComposeUIViewController {
App()
}
}
Intake the engine in your main.kt
fun main() {
// invoke it before the App() invocation
AmetistaEngine.intake()
application {
Window(
onCloseRequest = ::exitApplication,
title = "app_title",
) {
App()
}
}
}
Intake the engine in your main.kt
@OptIn(ExperimentalComposeUiApi::class)
fun main() {
// invoke it before the App() invocation
AmetistaEngine.intake()
ComposeViewport(document.body!!) {
App()
}
}
The next, and the last, step is fire-up the engine. You have three different options to fire-up it, but the only requirement is place the fire-up procedure in your App.kt script file
You can locate the "ametista.config" file in custom path, but the structure of the file must be the same, then fire-up with the dedicated method:
fun App() {
ametistaEngine = AmetistaEngine.ametistaEngine
ametistaEngine.fireUp(
configPath = ,
host = AmetistaConfig.HOST,
serverSecret = AmetistaConfig.SERVER_SECRET!!,
applicationId = AmetistaConfig.APPLICATION_IDENTIFIER!!,
bypassSslValidation = AmetistaConfig.BYPASS_SSL_VALIDATION,
debugMode =
)
MaterialTheme {
Column(
modifier = Modifier
.fillMaxSize(),
verticalArrangement = Arrangement.Center,
horizontalAlignment = Alignment.CenterHorizontally
) {
Text(
text =
)
}
}
}
If your application has multiple targets you can locate the configuration file in the common resources:
commonMain
|-- composeResources
|-- files
|-- ametista.config
then fire-up the engine with the dedicated method:
@Composable
fun App() {
LaunchedEffect(Unit) {
val ametistaEngine = AmetistaEngine.ametistaEngine
ametistaEngine.fireUp(
configData = Res.readBytes(FILES_AMETISTA_CONFIG_PATHNAME), // files/ametista.config pathname
debugMode = false // whether the issues or the stats collected have to real counted or just simulated their sent,
// make sure that in production is set on *false*
)
}
MaterialTheme {
Column(
modifier = Modifier
.fillMaxSize(),
verticalArrangement = Arrangement.Center,
horizontalAlignment = Alignment.CenterHorizontally
) {
Text(
text =
)
}
}
}
To enable the tracking of this analytics, you must integrate the Engine into your HTTP client (or a similar component)
to count the requests.
For example, you can do this by adding an interceptor, such as with Ktor
or OkHttp.
Independently of your HTTP client the Engine integration is the following:
...
your_interceptor_scope {
val ametistaEngine = AmetistaEngine.ametistaEngine
ametistaEngine.notifyNetworkRequest() // will be automatically sent and counted
}
...
And that's it! The Engine is fully integrated on your clients and working in coroutines it will not affect your application main workflow
To connect the specific platform for your application you need to invoke the related method as following:
@Composable
fun App() {
val ametistaEngine = AmetistaEngine.ametistaEngine
// after engine initialized
ametistaEngine.connectPlatform() // running on Desktop for example
MaterialTheme {
Column (
modifier = Modifier
.fillMaxSize(),
verticalArrangement = Arrangement.Center,
horizontalAlignment = Alignment.CenterHorizontally
) {
Text(
text = "Hello World!"
)
}
}
}
The method automatically detects the platform on which the application it is launched and connects with it. For example, if launched on a desktop, it will connect with the Desktop platform and so on for other platforms.
Once the platform has been connected, you can remove the method invocation for that platform to prevent retry attempts to connect to the same platform, or you can connect other platforms and follow the same procedure phases
If you need to inform the users about the tracking activity or performance monitoring of the Ametista-Engine you can use this template and customize it as you need
If you need help using the library or encounter any problems or bugs, please contact us via the following links:
Thank you for your help!
If you want support project and developer
If you want support project and developer with PayPal
Copyright © 2025 Tecknobit
repositories {
...
maven { url 'https://jitpack.io' }
}
repositories {
...
maven("https://jitpack.io")
}
Add the dependency
dependencies {
implementation 'io.github.n7ghtm4r3:Ametista-Engine:1.0.4'
}
dependencies {
implementation("io.github.n7ghtm4r3:Ametista-Engine:1.0.4")
}
dependencies {
implementation(libs.ametista.engine)
}
This file contains sensitive information such as server addresses, server secrets, and application-specific data.
To protect this data:
.gitignore for Git).sync the project and then you can access to the generated internal AmetistaConfig fileLike the gradle.properties file, also this file contains sensitive information such as server addresses, server secrets, and application-specific data.
To protect this data:
.gitignore for Git).{
// required if any specific versions are not specified
"app_version": "X.Y.Z",
// general version to use if the specific one for a target is not specified
"android": {
// not required
"app_version": "Y.X.Z"
// specific target version to use
},
"ios": {
// not required
"app_version": "Y.X.Z"
// specific target version to use
},
"desktop": {
// not required
"app_version": "Y.X.Z"
// specific target version to use
},
"web": {
// not required
"app_version": "Y.X.Z"
// specific target version to use
}
}
| Crypto | Address | Network |
|---|
| 3H3jyCzcRmnxroHthuXh22GXXSmizin2yp | Bitcoin | |
| 0x1b45bc41efeb3ed655b078f95086f25fc83345c4 | Ethereum | |
| AtPjUnxYFHw3a6Si9HinQtyPTqsdbfdKX3dJ1xiDjbrL | Solan |
Surfaced from shared tags and platforms — no rankings paid for.