User Tools

Site Tools


web:accesswebstories:access_webapp_stories

This is an old revision of the document!


Access Web App - 2.0

Prerequisite: Read Access Web 2 Overview as background information for these stories.

(Stories are number continuing from the WebApp 1.5 update task).

Things to consider for development:

  • Preserve current implementation.
  • Deliver functionality incrementally.
  • Detect mobile vs. desktop for UI flexibility.

Story 2.5 - Complete the prototype

Finish the prototype implementation, and blend the Click system with the Angular system. This would allow the two application systems to coexist, but will take some more development effort upfront with an incremental effort as releases are made.

The motivation for this story is that the user can go to “access.agtek.com” and still get to the same application, except now they have access file whereas before they had projects/machines/users/licenses. The user of this release is the app developer. The “access” portion is just a page that shows the Angular/Rest page is working correctly with the Legacy Click.

Story 3 - Access

Current user gets access files added to the existing application.

Story 4 - New Projects View

This supersedes the reworked project page (1.5) that's currently up.

I'm warming up to single application page for Projects as well although you can certainly tell me reasons we should not. As I worked on this I realized quite a bit is the same data just viewed differently.

  • Default Page is Map View out of the box with the option to switch to the panel design. Retaining user preferences of which view

Picture below is very rough but I like the theme for a single page web app that we can dive down with.

Story 5 - Uploader for Access

This leverages the new Access Web client to allow anybody chosen (via email) the ability to upload files to the designated Folder. Features include:

  • Selecting the folder to upload, interface to send an upload link to multiple email.
  • Upload page based upon link sent
  • Notification of link sender that upload has been initiated (page opened, actual upload start?)
  • Time limits and removing link availability (resending?.

Interfaces

Project/File Access Interface

The interface for sending a link should be fairly straightforward. Files being uploaded go in whatever folder is picked. Selecting the “Send Upload Link” (fontawesome cloud-upload-alt - not perfect but . .) brings up a window asking for the email addresses and how long the link is active (default 7 days).

Upon pressing Send a link to the temporary upload page is generated and the email sent (can it be from the email of the user instead of access?)

Email Format

Temporary Upload Page Interface

Upon opening of the page (or upload of a file. I don't know what we can discern) send an email to the link sender notifying them that something like an upload is being done. Bonus points if we can link to the folder it happens to in Access. The Upload page needs the following:

  • Upload button for selecting files via user interface
  • Large Drag/Drop area for files
  • Feedback on file upload success/failure

Element Scratchpad

Form to generate emailed and randomized link to recipient. Specifying where it goes in Access? Notification of end consumer that new data is there. Where do we trigger it from in Access. Just allow Write not view

* Summaries
* Day detals
* Sub-cards (3/4)

Story 5 - Machines and Trackers

Machines and trackers

Story 6 - Users and Licenses

Users and Licenses - Replace current capability

Story 7 - Reports

Reports = Replace current capability.

web/accesswebstories/access_webapp_stories.1519697655.txt.gz · Last modified: 2018/02/27 02:14 by mikeclapp