<< back

Android Messages 3.1.0

Android Messages as a Cross-platform Desktop App

Category: Social Networking
Price: Free
Popularity: Low
Version String: 3.1.0
Release Date: 2019-11-27
Architecture: Intel & AppleSilicon(ARM)
Minimum OS: macOS 10.14.0
Vendor Name: Chris Knepper
Homepage: github.com

Version History 3.1.0

#{version_history}

Description:

ANDROID MESSAGES DESKTOP


Run Android Messages as a desktop app, a la iMessage. For those of us
that prefer not to have a browser tab always open for this sort of
thing.

NOT AFFILIATED WITH GOOGLE IN ANY WAY. ANDROID IS A TRADEMARK OF GOOGLE
LLC.

Disclaimer: I have tested this with my Pixel on both macOS High Sierra and Windows 10. Normal functionality seems to work, but help testing and feedback is greatly appreciated!

Inspired by:

- Google Play Music Desktop Player
- a Reddit post on r/Android

Based on:

- electron-boilerplate



DOWNLOAD


Head over to the latest releases page! * For Mac, choose the DMG * For
Windows, choose the EXE * For Linux, choose either the DEB, the SNAP,
the PACMAN, or the APPIMAGE. If you’re using Arch or derivates of, it’s
also available in the AUR.

IMPORTANT NOTE: The Windows app binary isn’t signed. This doesn’t seem
to be a big problem, but please report any issues you run into on
Windows that may be related to signing.

IMPORTANT NOTE 2: We currently have builds for Windows and macOS, and
Linux. I test releases on macOS, Windows 10, and Ubuntu Linux. I would
love help testing on additional distros of Linux and other versions of
Windows.



FEATURES


- System notifications when a text comes in
- Notification badges on macOS
- Spellchecking in ~50 languages
- Run in background on Windows / Linux / macOS
- Minimize to tray on Windows / Linux
- Menu bar support on macOS
- TBD…



SPELLCHECKING


Implemented via the amazing electron-hunspell library with dictionaries
provided by the excellent dictionaries project. Language files are
downloaded when the app opens and the language used is based on the
language set in your operating system. If you switch your system
language and restart the app, the spellchecking should occur in the new
language as long as it is in the list of supported languages.



TODOS / ROADMAP (ROUGH ORDER OF PRIORITY):


- ☒ Make sure it actually works (definitely works as of v0.1.0, done
via 8068ed2)
- ☒ Release signed binaries for macOS (binaries are signed as of
v0.0.2, done via 8492023)
- ☒ Make an icon (done via df625ba)
- ☒ Remove left-over code from electron-boilerplate (done via 4e7638a)
- ☐ Correct tests
- ☒ Release packages for Linux (done via 41ed205)
- ☒ Handling updates (done via 625bf6d)
- ☒ Platform-specific UX enhancements (i.e. badges in macOS dock)
(this specific enhancement is in as of v0.1.0, done via 8068ed2) UX
ENHANCEMENTS AND FEATURES ARE NOW BEING WORKED ON WITH ISSUES
SUBMITTED BY USERS
- ☐ Release signed binaries for Windows
- ☐ Make a website? (if it gets popular enough)
- ☐ Support customization/custom options a la Google Play Music
Desktop Player?



DEVELOPMENT


Make sure you have Node.js installed, then run the following in your
terminal:

git clone https://github.com/chrisknepper/android-messages-desktop.git
cd android-messages-desktop
npm install
npm start


Starting the app in development mode

npm start



TESTING


Run all tests:

npm test


Unit

npm run unit

Using electron-mocha test runner with the Chai assertion library. You
can put your spec files wherever you want within the src directory, just
name them with the .spec.js extension.


End to end

npm run e2e

Using Mocha and Spectron. This task will run all files in e2e directory
with .e2e.js extension.



PUBLISHING A RELEASE:


1. Commit what you want to go in the release (including updates to
README and CHANGELOG)
2. Run npm version where is either major, minor, or patch
depending on the extent of your changes (this command increments the
version in package.json and creates a git tag for the new version)
3. Run git push
4. Run git push --tags
5. Run npm run release (for this step to succeed, you must have a
GitHub Personal Access Token with write access to this repository in
your PATH as GH_TOKEN)
6. Go to GitHub and publish the release (which should be there as a
draft), taking care to make the release name match the tag name
including the “v”

Once the packaging process finished, the dist directory will contain
your distributable file.

We use electron-builder to handle the packaging process. It has a lot of
customization options, which you can declare under 'build' key in
package.json.



THE ICONS


We use png2icons to create Windows and Mac icons from the source PNG
icon, which is located in assets/android_messages_desktop_icon.png.
However, the Windows icon generated from this package seems to result in
visual corruption on Windows 10, so I’m manually converting the PNG to a
Windows icon with icoconvert.com for the time being.