We need to find a solution to needing to update the SUI tools periodically in the backend server. Hopefully, we can create a script that updates the took every so often. We just need to make sure that the update will succeed under the normal specs of the server.

The listing of the modules is still not as intuitive as we would like.

the users should be able to enter a transaction digest to add all created objects and packages to the deploy canvas.

The pictures in the feature carousel in the landing page get too big when the page is view with a big window. We need to add a max height or width to the pictures.

We are currently truncating long word but it would be better if we can wrap them

The current landing page is acceptable but it is very basic. I think we can work on a new design that is more professional, and very cool.

Update the icon on the website to the new icon used by the twitter account. The new one will match better in the site.

There is a slight bug where the wallet has to be disconnected, before the same wallet can be authenticated for a new network.

We need to get all of the wallets working with testnet. Currently Suiet wallet is the only wallet that we can detect the network change.

In the deployment page, when we display all of the functions, we should have a section for entry functions.

The toasts on the build page will only show up when there is an active module up

Currently, when switching functions, the previous arguments stay there. We need to clear it when the function switches.

We are thinking that there are two many themes. We agreed to get rid of the majority of the light themes and some of the dark mode themes.

Currently there is no indication that the package is being compiled when a user clicks compile. We should add an "Compiling..." toast similar to our in progress toasts for deployment.

Make the IDE compatible with the Aptos move and Aptos network.

To do this, I think we can do the following:

• Add a global variable to keep track of which chain we are on and add the ability to switch between the chains.
• Create code syntax highlighting for the Aptos version of Move
• Create an Aptos version of the backend functionality

To think about:

• We could have a a slight different in design for the two protocols.
• Remember that Aptos has main-net up so we will need to do testing for both test and main-net.

We have requests to make the IDE compatible with the Sui testnet as well.

This could potentially be a premium feature

Evan was saying that it would be best to have tabs for modules that are currently being worked on or view. He was saying that we should have the module list in the sidebar. This would be better since this is typically what developers are used to.

For some reason, the landing page width goes beyond the width of the screen. The users are able to scroll to the right to see some empty canvas.

I think the potential fix to this could be to add an 'overflow: hidden' or something similar to the css of the landing page.

There current syntax highlighting for the Sui move editor is pretty basic and incomplete. We need to polish the highlighting. We could maybe find some documentation or code describing the syntax of the language and use that as a guide.

There is a typo in the confirmation message.

I think it might be nice to require a confirmation before refreshing the deployment page. Refreshing would remove all of the objects from the canvas so it might save the user in case of an accidental refresh.

The information in the dependency table in the build page should also be wrapped like the information in the deployed object tables are

There are a lot of options of testing features offered by the move testing framework. We should make sure we offer all of the options. I was thinking that this would be a good time to start on the testing page, but I do think this could all be options in the settings section. I think this is the plan at the moment.

I think it would be nice to show the x icon on tabs over hover for the tabs that are not the active tab.