TeamAmaze / TeamAmaze/AmazeFileManager

CloudRail APIs are getting decommissioned

Open
#1,593 3 comments 0 reactions 1 assignee View on GitHub

@EmmanuelMess is already working on this.

Since Jan 11, 2020.

Area-Cloud Issue-Discussion Issue-Severe (high)
Dominant language
Kotlin
Stars
6.4k
Forks
1.7k
Avg merge
3d 9h
Merged PRs (30d)
1

Description

I'll quote the mail I received few days back below.
Please post new suggestions or we might have to pull down Cloud plugin from play store.


Dear CloudRail user,

We will discontinue our cloud connector (unified APIs) products as of March 1st 2019. This means that we hereby cancel all contracts with you, won't update the SDKs and don't offer support for this product anymore.
This step affects all users of the Community, Basic, Premium and Professional plans, but not our enterprise customers which we already reached out to over the last weeks.
Feel free to continue using the SDKs in your current products as long as they don't break due to API changes. This service is of course now provided as it is, without any guarantees or support.

Here are the two main reasons why we did it:

  1. This step allows us to entirely focus on our products for the industrial automation space (https://iot.cloudrail.com).

  2. We achieved an impressive reach with our unified APIs, but in the end most users chose the free community or a pretty low priced plan. Unfortunately these users still demanded a very high level of support which we were not able to provide giving the low revenue generated by them.

We thank you very much for trusting in our Unified APIs and hope that the merge to alternative solutions won't cause too much trouble.

The CloudRail Team

==============================================
CloudRail
licobo GmbH
Julius-Hatry-Str. 1
68163 Mannheim
Germany

Email: support@cloudrail.com

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.