Skip to content

MVP Requirements #3

@arthurvergacas

Description

@arthurvergacas

While we work on the Vinum Compiler side of things, it is also important to have an MVP of the application working.

We can use this issue to discuss what and what not needs to be done in order to achieve this.

To me, the main use case looks something like:

Based on that, some of the points that, in my opinion, seem to be essential to a first MVP are:

  • Basic user authentication to allow individual documents
  • Document persistence
  • Document download (as PDF, plain text, etc)

What are your thoughts? Do you think we don't need something from this list? Do you think I missed something??

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions