damiensedgwick / floop

Floop eliminates the stress of building and managing your own feedback system by giving you a platform to build off of.

Hello 👋

I am a software developer based in Norwich, UK and I am currently hacking on Napp and Feature Flicks!

Projects

Developing

• Feature Flicks - API driven feature flags.

Thriving

• Napp - Nano App command line tool.

Retired

• Floop - Feedback collection made easy.

Socials

• Website
• LinkedIn
• Polywork

floop's Issues

Implement Dashboard Feature

This is the main screen of the application. It should display the following data points:

• Current rating
• Rating graph to show ratings over time
• Latest submission, this could be an issue or feedback

Implement Users

The user should be able to see a list of other users and if they have the correct permissions, make edits to the other users.

• Users should be a scrollable list
• A user should be editable if the authenticated user has the correct permissions

Settings page

Implement reporting page and functionality

fixed off center hero for xl screens

table accessors are snake cased

these should be formatted properly for a better ui.

create welcome emails for new users

on the team page, I should not see / be able to delete my own user

Ratings page

Snag list

• Should be able to sign in using a variety of methods
• User should be able to log out easily
• User should be able to delete their project
• User should be able to invite team members

Users page

Implement Issues

This screen should enable a user to scroll through all of the recent issues.

• Issues should be a scrollable list

Dashboard page

Test issue

I would expect this issue to appear in my projects board!

Implement Organisation

When a user signs up, this should also create an organisation of which they are the owner of.

• when a user registers, this creates an organisation
• refactor auth code to use MVC

Widget creation

• Widget is installable as a NPM package for a React component
• Widget can handle Rating, Issue and Suggestion submissions

Redirect after sign up should go to the dashboard

Confirming your email takes you back to the landing page, be nice if it could redirect through to the dashboard?

Navigation / Pages take 2-3 seconds to load

Going through the left navigation links takes 2-3s or so to load after clicking each page, would be good to see a loader cause I thought it was broken at first. Not sure why it takes so long though?

Test

Issues page

Replaced heroicons with ones from figma

All of the icons can be found here Untitle Icons

Test Issue Number 2

I expect this one to show on the board!

added open graph attributes

Suggestions page

add widget demo to marketing page

Provide a documentation link from the dashboard

I’d love a link to docs from within the dash to save my lazy ass some time looking

Submissions setup

Implement Feedback

This screen should enable a user to scroll through all of the recent feedback.

• Issues should be a scrollable list

getting started section does not scroll on mobile

Fixed by applying the tailwind prose class to the components using the code block.

investigate automatically creating a gh issue from an issue

when a new issue has been received, it would be good to automatically create a gh issue.

this would have to be enabled by the floop user and it would be good if this worked with github,
gitlab and bitbucket for max compatibility.

Refactor Bottom Navigation

The bottom navigation could likely do with refactoring to make sure duplication is removed and that it is easy to read and follow.

• It should follow the data, domain and presentation architecture pattern being implemented

Profile page

investigate an onboarding flow for new users

Refactor Authentication

The current sign in flow creates some duplication between the registration form and the login form. Some refactoring work was started to use only one form for both views, however, a parameter would be needed to dictate whether or not the user would be signing in or registering an account.

As the decision has now been made to user the following project structure:

/ lib
--/ src
----/ features
------/ example
--------/ data
--------/ domain
--------/ presentation

It would be good to refactor the current authentication flow further so it fits into the above architecture.

• Authentication code duplication has been reduced
• A single authentication process can now be used to logging in or registering an account

Improve sign up emails

Signup emails could do with some dazzle dazzle

Implement Settings

This screen will be for controlling the global settings of the account. Admittedly, I do not know what these are or will be at this point in time. This screen may be removed if it is not deemed necessary.