LogoLogo
Back to our website
  • Session Messenger
    • Installing Session
      • Installing on Linux (Debian based distros)
      • Installing Session using F-Droid
      • Installing Session using APKs
      • Installing beta versions of Session
    • Advanced Features
      • Communities
        • How to setup a Session Open Group Server (SOGS)
        • Creating a read-only channel using SOGS
      • Session Names and the Session Name Service (SNS)
        • Registering an Oxen Name using the Oxen Name Service
      • Session Pro
    • Contribute to Session Messenger
      • Development
      • Localization
  • Session Token (SESH)
    • Tokenomics
      • Genesis tokenomics
    • Rewards Programs
      • Service Node Bonus Program
      • Oxen Coin Claims
      • Testnet Incentive Program
    • Get Session Token (SESH)
      • How to create a crypto wallet
      • How to view SESH in your Wallet
      • How to use Session Token (SESH)
  • Session Network
    • Session Nodes
      • Staking and collateralization
      • Incentivization
      • Consensus
      • Swarms
      • Session Appchain
      • Deregistration
    • Session Protocol
      • Onion requests and message routing
      • Account IDs and self managed keys
      • Account restoration
    • Staking
      • Staking Reward Pool
  • Contribute to the Session Network
    • Frequently Asked Questions (FAQ)
    • Testnet
      • Staking to a Session Stagenet Multicontributor Node
      • Session Stagenet Node Setup
        • How to set up an oxend L2 proxy
  • Twitter / X
  • Discord
  • Session Token Website
  • Session Website
  • Session Whitepaper
Powered by GitBook
On this page
  • Contributing to development of Session iOS
  • Contributing to development Session Android
  • Contributing to development Session Desktop
  • Contributing development to other parts of the Session ecosystem
  • Reporting bugs from Session
  1. Session Messenger
  2. Contribute to Session Messenger

Development

Last updated 28 days ago

All of Session’s code is completely open source and available on GitHub. Several key Session repositories are managed by the Session Technology Foundation as part of its role as steward. You can find these repositories . All you need to start contributing is a GitHub account and some development knowledge.

Contributing to development of Session iOS

Session’s iOS client is written using Swift. If you are familiar with Swift, then you can likely contribute to Session on iOS.

You can find a list of known issues and feature requests . Many of these issues contain tags and comments to help you find an issue that suits your skills and experience level.

Contributing to development Session Android

Session’s Android client is predominantly written using Kotlin and to a lesser degree Java. If you are familiar with Kotlin, then you can likely contribute to Session on Android.

You can find a list of known issues and feature requests . Many of these issues contain tags and comments to help you find an issue that suits your skills and experience level.

Contributing to development Session Desktop

Session’s Android client is predominantly written using TypeScript. If you are familiar with TypeScript, then you can likely contribute to Session on Desktop.

You can find a list of known issues and feature requests . Many of these issues contain tags and comments to help you find an issue that suits your skills and experience level.

Contributing development to other parts of the Session ecosystem

Other parts of Session’s ecosystem, such as the , , and Node software (which handles Session’s backend) can be accessed and contributed to on GitHub. However, note that the documentation for issues and requests is not rigorous, so it may be difficult to find areas of work in need of contribution.

Reporting bugs from Session

Bugs can be submitted through Session’s helpdesk portal or via the issues section in the relevant GitHub repository ( | | ).

The form will ask for some details about the issue you are encountering, the version of Session you are using, and your device. Additionally, you can attach your logs to give developer contributors more useful information when they investigate the issue.

To export your logs, go to Session’s in-app settings, go to Help, then Export Logs.

here
here
here
here
docs
websites
here
iOS
Android
Desktop