Note

Depends on Issue #12

• Open up an iMessage window when option is selected for SMS contact

• Open up Skype when option is selected for Skype contact

Details:

Can use AppleScript to open up and use Apple tools

Command:
For direct message from:

osascript -e 'tell application "Messages" to send "Hello World" to buddy "J D McIninch"'

For opening the GUI:

open -a Messages - see if you can pre-populate with the number.

onChange can have issues with copy+paste on certain platforms (including, apparently, electron.) Migrate away by changing the tag.

Migrate raw magic numbers to constants in the common/constants.js file.

Otherwise new logins break.

It's really ugly right now. Pls make pretty, thx.

Apple-ish background and colors with the polite.li logo.

How do we update the statuses?

Ideas:

• On status hover, refresh individual user.

• On timer, refresh all users

Any others?

Like this:
https://github.com/maxogden/menubar

Occurs on branch "contact", currently unmerged.

Contact profiles are links to your contact information.

For instance - 555-555-5555 for TEXT, 111-111-1111 for PHONE, @akhilcacharya for SKYPE

Idea: Menu bar setting, opens new window, allows you to add information for each preset data type.

Set it to be fixed, along with changes to the sorting dropdown.

Also:

The scrollbar disappears once you click/focus the search bar and start scrolling. FIX.

By:

• Last updated

• Last contacted

• Most contacted

Migrate all of the constant option objects with a constant file or everything.

Do this for all references, in menu, etc.

Create it using the GiHub automatic page generator.

https://github.com/akhilcacharya/polite.li/settings

Be sure to:

• Include a screenshot

• Explanation

• (At the end) link to installable release

Instead of 1 input opening up another, typing anything in the 1st input will be saved as a custom status.

Currently, new users don't seem to have gravatar images. Fix.

Originally this was supposed to be a x-platform app, but scope changed a bit. lets change the UI similarly.

• Bigger text/bigger buttons - make it more obvious what the function of the button is

• Use images on the buttons instead of emojis.

• Add link to GitHub in the user login

TODO:

• Fix scrolling

• Status after status update - for feedback (use animation)

• Look over Heuristics for good UI

• Add more users

Cuz why not

Have this before we do an MVP demo to Dr. St. Amant.

Abide by Neilsen:

• Visibility of system status
• Match between system and the real world
• User control and freedom
• Consistency and standards
• Error prevention
• Recognition rather than recall
• Help users recognize, diagnose, recover from errors
• Help and documentation

By Shneiderman:

• Strive for consistency
• Enable frequent users to use shortcuts
• Offer informative feedback
• Design dialogs to yield closure
• Offer error prevention and simple error handling
• Permit easy reversal of actions
• Support internal locus of control
• Reduce short-term memory load

By Norman's 7 Principles:

• Use both knowledge in the world and knowledge in the head.
• Simplify the structure of tasks.
• Make things visible...
• Get the mappings right.
• Exploit the power of constraints...
• Design for error.
• When all else fails, standardize.

Use https://github.com/orgsync/react-list.

Front-end is done, backend is not. Add to syncing procedure.

Considering using a "P", thoughts?

Make the original one a 512x512

Edit: @kaveenherath linked these:

http://iconion.com/
https://iconsflow.com/editor

Abide by these:

https://docs.google.com/presentation/d/1_GahUrpVklwRcN0MtIqWMssSg3smstOCLFo2GUkaXu8/edit#slide=id.p72

https://docs.google.com/presentation/d/13QTy69w8uzEQK4NyUuEGUzbVruSZHSq2PcX03mOMwww/edit#slide=id.p9