copyandpaetow / lovable-survey-creator Goto Github PK

A small tool to create delightful surveys and analyze the results.

View the website | Report a bug | See a test survey

• About the Project
• Usage
• Roadmap

This is a vue-coded learning project and a future method of testing upcoming apps/features to get feedback early.

I was annoyed by the lack of good looking surveys + their builders and the lack of a mobile first thinking. Here I saw a learning opportunity.

Before creating a survey you have to signup (I know this is a barrier of entry but sadly, there is no way around it. Stuff has to be saved somewhere)

The app is structured in 3 tabs:

• View: Where you can see all your surveys and copy links from these surveys to clipboard
• Analyze: Here you can see how your App is performing
• Create: In a 3-step process you create a survey feature by (1) adding URLs and basic information, (2) adding questions and (3) previewing your feature. This step is repeated until you have sufficient features and publish it as a survey.

This will give you a survey like this: Test-survey (I hope you like salad :)

If you find anything in this code, which is not a best practice or at least acceptable in any way, please tell me and open an issue. This is at this state a learning app and I need the feedback to grow.

• At least one more question type (net promotor score (NPS) seems like a good fit for this)
• More auth-related features
  • like password-reset
  • password-requirements
  • a show password toggle
  • account-deletion

This could be a very long list but I will just state the most prominent bugs:

• after navigation between the different sub-tabs of "Analyze", the navigation to the other routes fails (and I don't know why)
• jumping navigation of the hamburger menu icon
• video-element starts with no height and pops up after loading. The definied poster gets not loaded early enough do fix this
• survey state object needs to be cleared after publishing
• "copy to clipboard" should only color the selected survey and not all of them

Because of so much progress during this project, some strategies and inputs came late into it and need to be established through out the whole app:

• different types of passing data between components (state vs props)
• incoherent CSS naming
• prop validation
• some components are to massive to properly maintain

Distributed under the MIT License.