Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SDK for Capacitor #71

Open
EinfachHans opened this issue Jan 24, 2024 · 4 comments
Open

SDK for Capacitor #71

EinfachHans opened this issue Jan 24, 2024 · 4 comments

Comments

@EinfachHans
Copy link

EinfachHans commented Jan 24, 2024

It would be awesome to have a Capacitor Plugin as a wrapper around the native iOS, native Android and web SDK

@EinfachHans
Copy link
Author

When you don't know Capacitor and/or need support, i can assist you with that 😊

@goenning
Copy link
Member

I'm open to a capacitor SDK, but I don't know anything about it.
How much work is it to build a wrapper?

@EinfachHans
Copy link
Author

EinfachHans commented Jan 26, 2024

@goenning Nice to hear 👍🏼

Capacitor is the a multi platform tool, which supports web apps, native ios and native android apps. In the native environments it works by starting a web view, where users are able to present a web frontend. Maybe you heard of Cordova before, it's like a way better successor.

The work should not be much. Capacitor provides a bridge between the web view and the native platform.

In general it's quite easy:

  • You have a definition of some methods in typescript
  • You optionally (would make sense in this case) have a web implementation, so typescript again, where we could use the js aptabase sdk
  • For both native environments you have a native file, so swift and java/kotlin, where we could use the native sdk's of aptabase.

So the only thing "to maintain" would be:

  • Update package versions from time to time (as far as i know you can configure the ios and android dependencies with a default and users can override that by theirself). But it's a good practise to update the default one always to the latest one
  • If something at the sdk changes (new method or arguments for example) the changes needs to be reflected

As i said i would love to assist you here if you want to 😊

@cristipufu
Copy link
Member

@EinfachHans feel free to start building the sdk in your own repo and we can transfer it afterwards

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants