Improve Gnodev

[moul]

Meta issue for listing ideas to improve Gnodev

• Make the README of gnodev display information on getting started.
• Link the README of gnodev from the top-level README and suggest gnodev as a tool for getting started with writing gno contracts.
• Include a documentation example on using gnodev with a service like ngrok or a tunneling service to share a local gnodev publicly, with or without docker.
• Consider using gnodev as a simplified "portal loop" for managing small projects (@gnolang/berty, or flippando).
• Create a proof of concept of a gnodev mobile/desktop app using gnonative. cc @gnolang/berty
• Work on a proof of concept of gnodev as a desktop app. (In progress feat: contribs/gnotray #1435)
• PoC of an integration with the playground.

Related with #1583

[costinberty]

We will do this one: "Create a proof of concept of a gnodev mobile/desktop app using gnonative. cc @gnolang/berty" in a few weeks as part of our joint (Gno - Berty) comm/mkt efforts around Gno Native Kit.

[jefft0]

Consider using gnodev as a simplified "portal loop" for managing small projects (@gnolang/berty, or flippando).

On the Berty test node, we're already running gnodev which reloads the GnoSocial realm on git pull. 😁
http://testnet.gno.berty.io/r/berty/social:jefft0

[grepsuzette]

Propose:

• command "h" in gnodev should mention a link to the full help of gnodev, which would be in docs/

(proposed in #2497)

[moul]

See #2866