You have a growing business with a customer base that relies on your timely deliveries.
This app connections your shipments to an optimized route reccomendation engine.
- FlowBy (Amazon Web Services EC2)
![[app]](/DougKong/flowby/blob/master/screenshots/app.png)
- Mean.IO (MongoDB, Express.js, Angular.js, Node.js)
- Twitter Bootstrap
- Grunt
- most of my development was on the client side.
- some of my data is hardcoded in either the client controllers or the server side controllers.
- the workflow of the app is driven by the 'drivers' section in the top left corner.
- when the number of drivers changes, the event is broadcasted to the other controllers via a service.
- the 'routes' section displays only the selected drivers and their associated shipments and routes.
- the 'map' section will display a route corresponding to each selected drivers.
- the main server side file I'm using is the shipments controller which sends back the shipments with information of which cluster they belong in. On the Client side I assign the cluster to an available driver.
- Promises: In my map controller promises were working ok for a single run but not when used repeatedly in a loop. I returned to using nested callbacks.
- External Libraries: I started using some Angular directives I found online but in the end I found that they didn't have all the functionality I needed.
- Clustering algorithms: I didn't know anything about this area so I did some research on the various algorithms available.
- Promises get promises working to clear callback clutter.
- MongoDB I setup and tested some of the database models but I didn't get to using them in the app.