Skip to content

Instantly share code, notes, and snippets.

@thesocialdev

thesocialdev/feedback-svportal-siggraph.md

Created November 7, 2017 17:21
Show Gist options
  • Save thesocialdev/c740bbef53a9d6888773636822d71706 to your computer and use it in GitHub Desktop.
Save thesocialdev/c740bbef53a9d6888773636822d71706 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
feedback-svportal-siggraph.md

Landing Notes about the SV portal

First of all, the software improved so much since the previous conferences and I am not the only one who have been saying that, so congratulations for all you have done.

I didn't see the software with failures or bugs, I see there was goals that couldn't be reached due the limited time and short deadlines so I want to contribute with my developer perspective and suggest some directions that the next technical team can take for the next year. I believe most of them you guys already know and I apologize if some feature already exists and I wasn't able to identify it.

What I missed

  • Some sort of dashboard with the main events of the day
  • A notification system that replaces the Facebook Group (Most wanted)
  • Responsiveness or Mobile application
  • A feature that export my shift calendar so I could import it automatically to Google Calendar
  • A notification when my shifts were reorganized
  • A link with the shifts and event map

UX issues

  • I had to login everytime I need a information from the portal
  • The calendar of the day should be at the home page (as info of the dashboard)
  • All the SV related events should be on the calendar

Cool ideas (Ok, this is subjective)

  • Gamefy the integration between the SVs
  • Orientation with GPS inside the event
    • It would be great to know where is the closest TL when seeking for help
  • Facebook bot (Pixel) that communicate the team with important messages

Technical questions

There were some details that I couldn't perceive due the rush of the conference and if they exist would be easier to accomplish

  • Are you using RESTful architeture?
    • Even without a mobile application this architecture is needed to allow this kind of integration in the future
  • The framework that you are using has OAUTH2 implemented?
    • It can fix some issues about login persistence and allow third party applications to run along the system

I am not here to point issues and go away. You can see above the Tech Stack I have been working for the last couple of years and I think I can help you solving the problems I pointed out.

  • GIT + Gitlab
  • Laravel 5.3+
  • PostgreSQL 9.4+
  • PostGIS
  • GDAL
  • QGIS Server
  • QGIS (Spatial Data)
  • RESTful
  • PHP 7
  • NGINX
  • Gitlab CI
  • Bash (DevOps)
  • Docker
  • Docker Compose
  • Angular 4
  • Openlayers 3 (Map)
  • HTML5
  • CSS3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment