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

Should we publish a full app under dual-licensing ? #116

Open
jmgeffroy opened this issue Sep 2, 2024 · 0 comments
Open

Should we publish a full app under dual-licensing ? #116

jmgeffroy opened this issue Sep 2, 2024 · 0 comments

Comments

@jmgeffroy
Copy link
Contributor

jmgeffroy commented Sep 2, 2024

I get a lot of requests for full LCP integrations. With what is already provided in Iridium and its demo application, such a full LCP integration is still reserved for developers who are already very familiar with LCP and can use the provided LCP APIs themselves.

We also get requests for features that are not available in the demo application (highlights, TTS,...).

**We have most of them in an unpublished application. Until now, we've integrated bits and pieces of this app into the Iridium demo app, which is based on the excellent Jideguru's Flutter Ebook App. While it was a fantastic start for a demo app, integrating advanced features is double workload for us.

So, would you be interested in a dual license of a full application that integrates Iridium, with:

  • Epub and PDF support
  • LCP support (Epub + PDF)
  • Basic OPDS browser
  • Currently supported platforms:
    • Android
    • iOS
  • Future platforms:
    • MacOS (in progress)
    • Web (TBD)
    • Windows (TBD)

The dual license would give you the assurance that support can be handled by other developers. Our team is so small that we cannot reasonably handle a lot of requests, as you have already experienced, unless we charge high fees, which is not really realistic in the ebook "industry".

poll

All feedback is welcome, thanks! Beyond the poll above, detailed comments are welcome!

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

1 participant