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

[FEATURE] Embed Flowser in "Interact" page #9

Open
bartolomej opened this issue May 15, 2024 · 6 comments
Open

[FEATURE] Embed Flowser in "Interact" page #9

bartolomej opened this issue May 15, 2024 · 6 comments

Comments

@bartolomej
Copy link

Issue to be solved

Currently the "Interact" page is not yet implemented. I believe it was meant to host a UI for interacting with the contract shown on the overview page.

Suggest A Solution

We at Flowser are already working on a web-based tool for easy interactions with the contracts on Flow blockchain with neat features like FLIX integration: https://interact.flowser.dev

I believe this is a perfect tool to for integration in contract browser "Interact" page.

What are you currently working on that this is blocking?

No response

@bartolomej
Copy link
Author

We actually already started working on this and have a WIP design specs and PR here: onflowser#1

We also predicted this integration in our latest grant ("adoption" milestone): onflow/developer-grants#260

@muttoni
Copy link
Owner

muttoni commented Jun 23, 2024

Could flowser expose an API with common scripts and contracts involved, and Contract Browser can submit a search for a given contract being loaded, and suggest the common interactions.

e.g.

  • I search "nonfungibletoken"
  • CB sends a request to Flowser with that contract/address
  • flowser interact has 10 scripts / tx's that use NonFungibleToken
  • flowser responds with those 10 scripts with pre-agreed on metadata
  • CB lists those interactions out, with links out to Flowser
  • Ideally in the future, flowser interact exposes an iframe and I can integrate in contract browser directly.

@muttoni
Copy link
Owner

muttoni commented Jun 23, 2024

In the meantime I've pointed "interact" tab to point to Flowser :)

image

will include in next release (as you can tell from screenshot working on Crescendo stuff!

EDIT: This is now live! View it in action :)

@bartolomej
Copy link
Author

Could flowser expose an API with common scripts and contracts involved, and Contract Browser can submit a search for a given contract being loaded, and suggest the common interactions.

e.g.

  • I search "nonfungibletoken"
  • CB sends a request to Flowser with that contract/address
  • flowser interact has 10 scripts / tx's that use NonFungibleToken
  • flowser responds with those 10 scripts with pre-agreed on metadata
  • CB lists those interactions out, with links out to Flowser
  • Ideally in the future, flowser interact exposes an iframe and I can integrate in contract browser directly.

Yes, this is definitely possible. Do you think it would be better to:

  • have a mixed experience where contractbrowser fetches and displays a preview of available interactions within contractbrowser.com and then links out to flowser in a separate page
  • or have the flowser directly embedded within contractbrowser.com as an iframe (as you mentioned in the last point)?

I think both would be possible with what we are trying to build tho. We are thinking the iframe embed approach would be the primary way to embed flowser in 3rd party websites, as we also proposed in the grant.

@bartolomej
Copy link
Author

In the meantime I've pointed "interact" tab to point to Flowser :)
...

Wow awesome update, love it!

@muttoni
Copy link
Owner

muttoni commented Jul 1, 2024

Yes, this is definitely possible. Do you think it would be better to:

  • have a mixed experience where contractbrowser fetches and displays a preview of available interactions within contractbrowser.com and then links out to flowser in a separate page
  • or have the flowser directly embedded within contractbrowser.com as an iframe (as you mentioned in the last point)?

I think both would be possible with what we are trying to build tho. We are thinking the iframe embed approach would be the primary way to embed flowser in 3rd party websites, as we also proposed in the grant.

Open to either option - I think from a UX perspective perhaps embedding via iframe is better because it avoids unnecessary back and forths between sites.

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

2 participants