Skip to content

Implement your own Shark ASAP application (3 of 5)

Jump to bottom
Thomas Schwotzer edited this page Jan 4, 2022 · 7 revisions

Step 3: Make you application a Shark Component

You application will do something useful and is an application by its own right. A messenger e.g. is also an application by itself no doubt about it. But a messenger could also be a part of a bigger application. Who knows? It would be a very good feeling if others would happily use your software, wouldn't it.

What would others need to use your application?

  • Its application programmers interface. Luckily, this API is already there.
  • Your used format to avoid conflicts with others. Not a big thing.
  • A way to instantiate your software. That requires a component concept.

Follow section Shark Component in our developer guide and make your application a Shark Component.

Once you are finished, you are ready to test your component.

Introduction

Developer Guide

  1. Setup
  2. ASAPPeer
  3. ASAPStorage
  4. Serialize your message
  5. P2P Security
  6. E2E Security
  7. ASAPHops
  8. ASAP settings
  9. Change Listener
  10. Utils
  11. SharkComponents
  12. Go Android

Docs & components

Build an app in five steps

Shark Apps / Components

Connection Management

  1. Introduction Connections
  2. Test Support
  3. TCP Connections
  4. Idle Connections
  5. EncounterManager

ASAP insides

Clone this wiki locally