Skip to content

swarnimcodes/nosave-chat

Repository files navigation

NoSave Chat

NoSave Chat is a small Android app for starting chats without saving a phone number first. Enter a number with country code, then open it in WhatsApp, Telegram, or Signal.

The app is built with Dioxus 0.7 and Tailwind CSS.

Features

  • Open WhatsApp chats with wa.me links.
  • Open Telegram phone links.
  • Open Signal phone links.
  • Mobile-first Dioxus layout.
  • Catppuccin-inspired Tailwind theme.

Requirements

  • Rust
  • Dioxus CLI 0.7
  • Android SDK, NDK, and emulator tooling
  • Tailwind CSS CLI

Useful targets:

rustup target add aarch64-linux-android
rustup target add x86_64-linux-android

Development

Common commands:

make serve
make android-build
make tailwind-watch
make install-apk TARGET=aarch64-linux-android

Run Tailwind in one terminal:

make tailwind-watch

Run the Android app in another terminal:

make serve

The generated stylesheet is committed at assets/tailwind.css because automatic Tailwind generation through dx serve --android may not run consistently in this project.

Build

Build a release Android App Bundle for ARM64 phones:

make android-release-bundle TARGET=aarch64-linux-android

Build an APK for local install/testing:

make android-apk-bundle TARGET=aarch64-linux-android

For release APKs with automatic icon replacement:

make android-release-build TARGET=aarch64-linux-android

Release workflow rule:

  • Version in Cargo.toml is used for local make release artifact naming.
  • Git tag releases must use v<version> and must exactly match Cargo.toml.
  • Example:
git tag -a v1.2.3
git push origin v1.2.3

This publishes NoSaveChat-v1.2.3-aarch64-linux-android-release.apk.

For x86_64 emulators, use:

make android-apk-bundle TARGET=x86_64-linux-android

Project Layout

assets/
  favicon.ico
  tailwind.css
src/
  components/
    hero.rs
  views/
    home.rs
    layout.rs
  main.rs
tailwind.css
Cargo.toml
Dioxus.toml

Notes

This app is currently mobile-only. It does not use Dioxus fullstack features. A future local history feature can be implemented with local device storage and does not require a backend.

About

No description, website, or topics provided.

Resources

License

Stars

0 stars

Watchers

0 watching

Forks

Packages

 
 
 

Contributors