Needs pagination in places like:

• watchlist
• alert list
• order history list
• holdings list

packages to consider:

• rummage_phoenix
• scrivener_ecto

same notifications as in #17(on-page notifications)

• Chrome Notifications
• OS X Desktop Notifications

Next Step
add appropriate variant of line to user_socket.ex:

requires migration changes

i18n support for Chinese

For the moment:
The balance will just disappear;
and purchasing power doesn't update.

look into the alert channel

top positioned push notifications about:

• alerts
  • successfully created/deleted alert
  • alerts triggered
• orders
  • order placed
  • order executed
  • order canceled

Remove user/pass method.
Support OAuths:

• Facebook
• Google
• Github

Next Step
add appropriate variant of line to user_socket.ex:

Map, compared to list, saves look up time.
Therefore, let's improve AlertManager module to use map as server state.
state format:
%{ "symbol1" => [list of alerts], "symbol2" => [list of alerts], ... }

Currently, it is just barely a list of alerts.

Documentation should include:

• App URL
• Introduction (ref: LinkedIn project intro)
• Deployment Instructions
• Programming Language: Elixir
• Technologies Involved: ReactJS, Phoenix Framework, WebScoket, Channels, GenServer

The following guidelines must be followed:

1. In your sever module, which, I suppose, pulls quotes from Alpha Vantage:
   broadcast to all channels that care about that symbol,

• event: "update_asset_price"
• message format: %{symbol: string, price: number}

2. In react components care about those data, implement callback:

• channel.on("update_asset_price", ({symbol, price}) => {....})

process payment/subscription.
Compare Stripe vs Paypal

UI Design:

OrderManagerServer Working Logic Flowchart:

• OrderManager
• AlertManager

Put server modules into subdirectory.

cache last updated price in database, so users don't have to wait for a second or two for the price to show up.

But this approach may not be the best, since it creates heavy load on the database, constantly updating every entry.

A better approach came across my mind for now, is to hold these records in memory via a GenServer instead of database.

test

Currently, we handle adding alerts by totally reload all the alerts from the database, as shown below:

Must create a function to add alert without a total reload.

test