Hello, i just checked your lovely project and i discovered you have some sections missing out like FAQ, about us, contact us and privacy policy. If you dont mind i will like to write that for you.
My email: [email protected]

Hello,

As you may have heard, Steemconnect rebranded/migrated to Hivesigner. Is there plans to create Hivesigner alternative?

Changes are minimal mostly end points which is single point now to: https://hivesigner.com

There should be constants for common errors and error messages.

• create errors folder and module
• add error constant for an expired access token
• add error constant for an invalid access token
• add error constant for a revoked access token

steemconnect-firebase-functions should be more modular.

• restructure the folder structure
• each folder should have its own index.ts file

The number of functions in steemconnect-firebase-functions has increased, so documentation shouldn't be placed in the README anymore.

• create in-code docs
• generate external docs based on it
• create docs in Markdown for each module
• generate external docs with MkDocs

There should be an interface for the result of a successful broadcast.

• create a BroadcastResult interface
• use this interface everywhere it makes sense

createOperation should be generic.

• make createOperation generic as soon as TypeScript allows rest parameters to be generic (see the issue: microsoft/TypeScript#10727)

When jsonMetadata is null, createComment doesn't produce correct operation.

• fix the bug by setting jsonMetadata default value BEFORE the actuall JSON.stringify() call

There should be a module for helper functions. Let's start with error checkers.

• add helper functions module
• add functions that check what given error is caused by

Make broadcasting a downvote more intuitive.

To do so, let's:

• create a createVote function which creates and returns a vote operation
• create a broadcastDownvote function
• refactor broadcastUpvote to use createVote

Operation creator functions should accept a single parameter - configuration object.

• create interfaces for them
• refactor operation creator functions to accept a single parameter - configuration object
• its properties should be immediately assigned to variables (via destructuring)

broadcastOperations should use access_token and refresh_token to reliably broadcast any operations to the Steem blockchain.

What do I mean by reliably?

• given correct access_token and refresh_token, this function should always broadcast given operation
• if access_token expired, it should get a new one using refresh_token and try broadcasting operation again
• maybe it should require the entire AccessTokenResponse object

Requires completely new broadcasting system!

Library consumer should have an easy option to implement revoking an access token.

• create a revokeAccessToken function

Each operation should have its own creator function.

• make creator functions for every type of operation
• refactor the broadcast functions to use these creators

There should be a function to delete a comment or a post.

• create a delete_comment operation creator
• create a broadcastDelete function

Library consumer should be able to easily update user metadata.

• create setUserMetadata function