Avatars, Node Status, Encrypted Images & Theme Parity

Community Testing Pre-release: Qortal Go

Avatars, Node Status, Encrypted Images & Theme Parity

This is a Qortal-Community test build of Qortal Go (mobile) based on the
current upstream code, plus these focused changes:

• Clickable chat avatars – user and group avatars in chat are tappable
  to open the corresponding profile/group info, matching Qortal Hub’s behavior.
• Node status icon – a visible node status indicator shows whether your
  node is connected/synced from within Go.
• Encrypted chat images – encrypted image messages in Q-Chat now decrypt
  and display correctly in Go, matching Hub/Extension behavior.
• Full theme support & Theme Manager – Light/Dark and custom themes are
  powered by the same canonical palette schema Hub and the Extension use, with
  a mobile-friendly Theme Manager that can import/export shared theme JSON files.
• Developer docs – DEVELOPMENT documentation to help contributors build
  and run Qortal Go from source.

⚠️ This is NOT an official Qortal release.
It is a community test build to gather feedback before proposing changes
upstream.

This pre-release includes everything from the earlier “Dev Docs, Clickable
Avatars, & Node Status Icon Parity” build, plus the encrypted image support
and theme/Theme Manager parity work.

---

Downloads

• Android: qortal-avatars-themes-fixes.apk

Install as usual for a sideloaded APK (enable “Install unknown apps” if needed).

---

What to test

Focus on:

• Chat avatars
• Node status
• Encrypted chat images
• Theme support & Theme Manager (Light/Dark + custom themes)
• (Optionally) Developer docs

You can reuse notes from testing the previous Go build; this one supersedes it.

---

1. Clickable chat avatars

In Q-Chat within Qortal Go:

• Open a group or direct chat with active messages.

• Tap on a user avatar next to a message.

  • ✅ Expect: a user info view/sheet opens (similar to Hub’s user info panel).

• Tap on a group avatar (where applicable).

  • ✅ Expect: a group info view opens.

Check:

• ✅ Scrolling remains smooth.
• ❌ Taps on avatars shouldn’t “steal” scroll in an annoying way.
• ❌ No dead taps or weird double-tap requirements.

---

2. Node status icon

On main screens of Qortal Go:

• Start the app with your Qortal node running and connected.

  • ✅ Expect: node status icon shows a “good/connected” state.

• Stop or disconnect your node and return to Go.

  • ✅ Expect: icon changes to an “offline” or “warning” state after a short time.

• If your setup supports a “connecting/syncing” state:

  • ✅ Expect: icon indicates “in progress” appropriately.

If tapping the icon opens more details, note what you see and whether it
matches expectations.

---

3. Encrypted chat images

This build includes the encrypted image fix for Q-Chat in Go.

Try these:

1. Receiving encrypted images from Hub/Extension/Go

   • From another device/account (Hub, Extension, or Go), send an encrypted image
     in Q-Chat (direct or group).

   • View the chat in Qortal Go:

     • ✅ Expect: encrypted image messages show with the appropriate encrypted
       styling/indicator.
     • ✅ If your account has permission/keys, the image should decrypt and
       display normally.
     • ❌ No stuck “broken image” icons if decryption should succeed.

2. Sending encrypted images from Go

   • From Qortal Go, send an encrypted image to another user or group.

   • Open the same chat in Hub and/or the Extension:

     • ✅ Expect: encrypted image appears and decrypts correctly there as well.

3. No-leak & failure states

   • If you deliberately test a case where the viewer should not be able
     to decrypt (wrong account, no keys):

     • ✅ Expect: a clear “can’t decrypt” / protected state rather than a
       half-loaded or plain image.

   • With poor connectivity:

     • ✅ No crashes or infinite spinners; messages resolve to a clear state.

---

4. Theme support & Theme Manager parity

Qortal Go now uses the same canonical theme schema as Hub and the Extension,
with a mobile-friendly Theme Manager and theme-driven surfaces (no stray
hard-coded colors in the main flows).

4.1 Light/Dark defaults

• Find the theme/appearance settings in Qortal Go (e.g. Settings → Appearance
  or similar).

  • ✅ Expect: controls to switch between Light and Dark modes.

Test:

• Switch between Light and Dark:

  • ✅ Expect:

    • App bars, bottom navigation, drawers, backgrounds, chat lists, message
      cards, and primary buttons all update consistently.

• Fully close and reopen Qortal Go:

  • ✅ Expect: your selected theme persists.

Compare with Hub/Extension:

• With all three on Light:

  • ✅ Expect: major surfaces (nav, cards, primary buttons) use the same palette
    values (layout differences are fine).

• Repeat with Dark.

4.2 Theme Manager: import/export & custom themes

Open the Theme Manager in Qortal Go (e.g. via Settings → Appearance → Theme
Manager):

1. Import from Hub or Extension

   • In Hub, export a theme JSON via its Theme Manager.

   • In Go, import that file:

     • ✅ Expect: no generic “invalid theme” errors.
     • ✅ Go’s UI updates to match the theme (nav bars, cards, primary actions).

   • Repeat with a theme exported from the Extension.

2. Export from Go

   • In Go’s Theme Manager:

     • Export the current theme as JSON.

   • Import this file into:

     • Hub → Theme Manager.
     • Extension → Theme Manager.

   • ✅ Expect: both accept and apply the theme without schema complaints and
     with visually similar results.

3. Create & use a custom theme

   • Use the Theme Manager in Go to:

     • Duplicate or create a new theme.
     • Adjust some colors (accent/background/headers).
     • Apply the custom theme.

   • ✅ Expect:

     • The app updates immediately.
     • After closing and reopening Go, the custom theme remains active.

4. Error cases

   • Try importing:

     • A non-JSON file.
     • A JSON file that is missing required theme sections.

   • ✅ Expect:

     • A clear error message (e.g. “not valid JSON” or a specific validation
       message).
     • The previously active theme stays applied.
     • No crash or blank/white screens.

---

5. Developer docs (optional, for contributors)

If you’re comfortable with dev tools:

• Follow the dev docs (DEVELOPMENT.md or dev section of README.md) from a
  clean clone:

  • Install prerequisites.
  • Run the dev build.
  • Launch Qortal Go on an emulator or physical device.

• ✅ Expect:

  • Instructions are complete enough to get to a running app without guessing.
  • Any gaps or platform-specific quirks can be reported back.

---

How to report feedback

Please report results (good or bad) in the corresponding Q-Community issue:

• Go parity issues:
  • #4
  • #5
  • #6

When reporting:

• Include:

  • Device model and Android version.

  • Whether you installed from the APK or a dev build.

  • What you were testing:

    • Avatars,
    • Node status,
    • Encrypted images,
    • Themes / Theme Manager,
    • Dev docs.

  • Exact steps to reproduce.

  • What you expected vs what happened (screenshots or short screen recordings
    are very helpful).

If you mention issues in Qortal chats, please also copy a short summary into
the GitHub issue so we don’t lose track of them.

Thank you for helping test this combined Trifecta parity slice in Qortal Go —
avatars, node status, encrypted images, and theming all working together on mobile.

Dev Docs, Clickable Avatars, & Node Status Icon Parity

Community Testing Pre-release: Qortal Go

Dev Docs, Clickable Avatars, & Node Status Icon Parity

This is a Qortal-Community test build of Qortal Go (mobile) based on the
current upstream code, plus three focused changes:

• Clickable chat avatars – user and group avatars in chat are now tappable
  to open the corresponding profile/group info, matching Qortal Hub’s behavior.
• Node status icon – a visible node status indicator has been added so you
  can quickly see whether your node is connected/synced from within Go.
• Developer docs – initial DEVELOPMENT documentation is included to make
  it easier for contributors to build and run Qortal Go from source.

⚠️ This is NOT an official Qortal release.
It is a community test build to gather feedback before proposing changes
upstream.

Downloads

• Android: qortal-docs-avatars-nodeicon.apk

---

What to test

Focus on chat avatars, node status, and (optionally) the dev docs.

1. Clickable chat avatars

In Q-Chat within Qortal Go:

• Open a group with active messages.
• Tap on a user avatar next to a message.
  • ✅ Expect: a user info view/sheet opens (similar to Hub’s user info).
• Tap on a group avatar (where applicable).
  • ✅ Expect: a group info view opens.
• Scroll through chat normally.
  • ✅ Expect: scrolling remains smooth; accidental taps on avatars don’t
    "steal" scroll in an annoying way.

2. Node status icon

On the main screens of Qortal Go:

• Start the app with your Qortal node running and connected.
  • ✅ Expect: node status icon shows a "good/connected" state (green or
    equivalent).
• Stop or disconnect your node and return to Go.
  • ✅ Expect: icon changes to an "offline" or "warning" state within a short time.
• If there is a "connecting/syncing" state in your setup:
  • ✅ Expect: icon indicates this "in progress" state.

If tapping the icon does anything (e.g., open a status view), please note the
behavior.

3. Developer docs (optional, for contributors)

If you are comfortable with dev tools:

• Follow the new dev docs (DEVELOPMENT.md or the dev section of README.md)
  from a clean clone:
  • Install prereqs.
  • Run the dev build.
  • Launch Qortal Go in your dev environment/emulator or device.
• ✅ Expect: instructions are complete enough to get you to a running app
  without guessing.

---

How to report feedback

Please report results (good or bad) in the corresponding Q-Community issue:

• Go parity issue: #4

When reporting:

• Include:
  • Device model and Android version.
  • Whether you installed from APK or a dev build.
  • Exact steps to reproduce any problem.
  • What you expected vs what happened (screenshots welcome).

If you mention issues in Qortal chats, please also copy a short summary into
the GitHub issue so we don’t lose track of it.

Thank you for helping test this Trifecta parity slice in Qortal Go!