Sunday, September 13, 2015

Nice MacroDroid review

Just sharing a nice detailed review by one of my users:

Many thanks for Kevin for taking the time to write such an extensive review.

Friday, August 22, 2014

Introducing MacroDroid Wear

MacroDroid 2.3.8 introduces support for Android Wear devices and includes a MacroDroid application for the Wear device that enables quick invocation of macros on your Android phone/tablet.

Using the Android Wear trigger from within the standard MacroDroid app on your phone you can add macros that can then be invoked from within the Android Wear app. For each trigger you can select an icon and the chosen macro name will then appear within the Wear app. The Android Wear Trigger also has options so that a macro can be invoked when an Android Wear device connects or disconnects.

The Android Wear application can be configured so it can be quick launched by swiping down from the top left or top right corner of you device whenever the screen is on. This allows you to quickly jump to your macro list without having to first navigate to and launch the MacroDroid application.

The Android Wear action can be used as follows:
  • Open a specific action on the Android Wear device.
  • Create an Android Wear notification with up to 4 customisable actions.
  • Cause the wear device to vibrate to a specific pattern.
  • Set the brightness on the wear device.
Most of these options are fairly obvious in their use, but the Android Wear notification is worth exploring a little more deeply.

The notification should be assigned a title and message text and up to 4 optional actions. Each enabled action will then appear as an option when you swipe left from the notification using the standard Android Wear mechanism.

The power of this functionality is best demonstrated by an example:

I commute to my office every day via train. When I arrive at the train station sometimes I want to enable the wifi hotspot on my phone, so I can work on my laptop. From time to time the trains will be cancelled or running late so in this case I want to email my boss to let him know I'll be running late due to the trains. Therefore I create a new macro as follows:

Trigger - Cell Tower(s) at the station
Action - Android Wear Notification - Arrived at station, (Action to enable hotspot, Action to email boss)

The action to enable hotspot and email my boss are linked to existing macros that I defined earlier on the device. These macros can use the empty trigger if they are only to be invoked via this route, or could have any other trigger if there are other ways they can be invoked.

Now every day when I arrive at the station I receive this notification on my watch so I can quickly enable the wifi hotspot if desired. On days when the trains are running late I can also quickly email my boss to let him know all without taking my phone out of my pocket.

This is just one simple example that I use, so I'd love to hear of any cool uses that you find for this feature.

Wednesday, June 11, 2014

Introducing the development team

I've had a few requests from users recently to find out a bit more about the development team behind MacroDroid, so I thought I'd create a quick blog post to fill you in.

The entire MacroDroid support and development team consists of just me and with that in mind I suppose I'd better give you a little more information on myself.

I'm Jamie, 35 and live in Kent (just outside London) in England. I've been programming since I was around 10 and I've been a full time developer for the last 14 years. I've worked on Android pretty much since it came out and have been working on MacroDroid for just over 2 years.

Its probably worth pointing out that all development and support of MacroDroid is done entirely in my spare time and regularly while commuting to London for my *proper* (pays the bills) job. At the moment I'm working in London as a full time Android contractor and actually have a second part time contract on the go as well, so I'm currently a bit squeezed on MacroDroid time (but I do try my best). It is my long term ambition to work full time purely on my own applications but sadly the economics of app development make this quite hard to achieve. On the positive side the Android development scene in London is buoyant right now so I can make a good living doing something I generally enjoy.

From a personal point of view I have a wife and two daughters aged 4 and 5 who keep my weekends fairly busy and on the rare occasion when I do have little (non-MacroDroid) spare time I enjoy playing a bit of online poker and chess. If anyone's up for a game of chess my handle on Chess Time is UndeadCretin.

Below is a link to my linkedin profile in case you're interested, or more importantly if would like to pay me lots of money to build you a cool android app :-)

Thursday, November 28, 2013

MacroDroid Variables

Having recently introduced MacroDroid variables I get a lot of requests for more information on what they are and how they can be used. This blog post will explore how you can use MacroDroid variables to enhance your existing Macro set.

What is a variable?

In simple terms a variable is just an identifier that can hold some kind of value. MacroDroid currently support three different types of variable as follows:
  • boolean - A simple true or false value (effectively on/off)
  • integer - A numerical value (whole number)
  • string - A literal sequence of characters.

What can I do with them?

There are a few different uses for variables as highlighted below
  • Add a constraint so that a macro will only fire if a variable has a certain value. In this way variables can be used like MacroDroid modes, without effecting the single global state.
  • Output the value of a variable into an SMS/email, pop up message etc.
  • Trigger another macro when a variable is set to a certain value.
  • Create simple counters so you can count how many times an event happens and then trigger another macro at a certain count.

Concrete examples

The best way to understand how to use MacroDroid variables is with some simple examples.

1) Log how many SMS have been received in a day

Macro 1: Count SMS
- Trigger: Incoming SMS (Any)
- Action: Set Variable sms_count + 1

Macro 2: Log SMS Count
- Trigger: Day Time Trigger 23:59
- Actions: Calendar - Log Event (value of sms_count)
              Set Variable sms_count = 0

At the end of each day the number of incoming sms will be written to the calendar and reset to zero, ready to count the incoming SMS for the next day.

2) Block/Unblock a macro from firing via SMS. The example macro to block is one that makes the phone buzz every 1 minute (for example if you want a regular buzz when running or similar).

Macro1: Block Buzz
- Trigger: Swipe screen (left to right)
- Actions: Set variable block_macro to true
              Pop up message "Macro Blocked"

Macro2: Enable Buzz
- Trigger: Swipe screen (right to left)
- Actions: Set variable block_macro to false
              Pop up message "Macro Enabled"

Macro3: Regular Buzz
- Trigger: Regular interval (1 minute)
- Actions: Vibrate
- Constraint: Variable (block_macro = false)

Sunday, November 3, 2013

Introducing the MacroDroid Blog

Welcome to the MacroDroid blog! Content coming soon....