Wednesday, March 13, 2013

How to Create GQueues Tasks in Chrome Without the Mouse

Many of you use the GQueues Chrome Extension to create tasks on the fly or for a particular web page you are viewing.  While this is certainly easier than opening up GQueues, using the extension still requires a lot of mouse clicking, which is less than ideal for those of you seeking maximum efficiency.

Thanks to a tip from the Google Gooru, you can actually create GQueues tasks from any website with your hands never leaving the keyboard.

Enter Chrome custom keyboard shortcuts!

Here's how to get started:

1. Install the GQueues Chrome Extension if you haven't already

2. In Chrome, click the Window menu, Extensions, scroll to the bottom and click Configure commands

configure commands
3. In the window that appears, click in the field and type the keyboard shortcut you wish to use to activate the extension and click OK.
keyboard shortcut
4. Now when browsing the web simply type your keyboard shortcut to bring up the extension. Type your task description and press enter to create it.

GQueues Chrome Extension create window
5. From the confirmation window, you can either press enter again to close it, or type i to insert a new task.
GQueues Chrome Extension confirmation window
This makes it super easy to dump all the tasks from your brain into your GQueues Inbox to sort and manage later.




Tuesday, February 19, 2013

Eating My Own Words: GQueues Switches from HTML5 to Native Mobile Apps

In a guest post on the Google Code Blog back in May 2011 I argued that an HTML5 web app was a viable alternative to native apps for businesses looking to provide a mobile offering for a rapidly evolving product with limited developer resources.

I was wrong.

Well, mostly wrong. At the time I had just finished the HTML5 mobile app for GQueues and earnestly believed this was the right strategy for the product and business. I had a long list of major features I planned to implement and knew that creating several native apps and supporting multiple mobile codebases would significantly slow down development. Iterating quickly had been key to the success of the product to that point, and as a solo developer I had to carefully allocate my time.  A single HTML5 web app that worked on all mobile platforms made the most sense.  At the time, other companies such as Facebook and Google were embracing the same strategy.

Going Native

Two weeks ago I launched GQueues for Android and am currently developing a native GQueues app for iOS - so it's time I eat my own words. Or at least explain my complete change in strategy. Although I am still the sole developer for GQueues, a number of discoveries and changes over the last two years led me to the decision to finally go native.

HTML5 Fragmentation

One of the purported advantages of an HTML5 web app is the ability to write a single app that works everywhere. In theory a mobile web app can work on any device with a browser.  And while this might hold true for the simplest apps, I discovered that apps such as GQueues that utilized the most advanced HTML5 features with offline capabilities faced the same fragmentation challenges as building for multiple native platforms.  Although most WebKit-based mobile browsers supported WebSQL databases (at the time), allocating storage space differed on various devices.  The speed of reading / writing to the database varied significantly by device, as well as the performance of JavaScript engines.  I discovered that no browser on any device was capable of handling an account with 10,000 tasks at the speed expected by typical users.  As users reported bugs with the GQueues mobile app I found myself making changes to accommodate various devices and browsers which defeated the whole purpose of the single web app.  On top of that, documentation for a browser's implementation of HTML5 features was sparse, making support a huge effort of experimentation.  In short, HTML5 is still a nascent technology and significantly behind native platforms in terms of speed, responsiveness, features and maturity.

Background Syncing

I completely underestimated the importance of having automatic background syncing.  With the HTML5 app users had to hit the Refresh button to retrieve any new data from the web.  And syncing didn't happen at all when the browser was closed and the app wasn't loaded.  In developing the web app I reasoned this was a small compromise to make to gain the other benefits of HTML5.  I was completely wrong.  Background syncing is paramount for a task management app like GQueues.  Users on the go expect their data to be current and available whenever they want, even without a network connection.  Meeting this expectation is really only possible by syncing in the background whenever a network connection is available and by utilizing push messaging provided by native platforms.   The limitations of HTML5 provided a poor user experience, whereas the robust background syncing in GQueues for Android is one of users' favorite features.

Mobile Landscape

The mobile landscape has changed quite a bit in the last two years. In 2011 smart phones were just beginning to tip and the market was young and ripe with opportunity.  Many companies were competing for smartphone market share. Android was just beginning to take the lead, while BlackBerry and iPhone vied for the second spot.  Many devices still ran Windows Mobile 6.5 and even Palm webOS was at the table (remember them?). Now the market has consolidated with Android a clear leader and iOS claiming the remainder. Today a business needs their product on only two mobile platforms to cover 88% of all mobile users. This is much more feasible (even for a solo developer like me) than creating 4 or 5 different mobile apps, or betting on the wrong one.

Product Evolution

The HTML5 strategy did prove valuable in one area - it allowed me to continue rapidly adding features to GQueues without being slowed by maintaining multiple mobile apps. GQueues is a much more mature product now than it was two years ago. While I will continue iterating based on user feedback, GQueues has a much larger core feature set now, which makes the initial versions of the native apps more useful and provides a stronger base to build on.

User Demand

The most eye-opening discovery I made regarding native apps was the enormous user demand from GQueues customers. Last May I surveyed all GQueues users and asked what new features they wanted most. A native Android app was at the top of the list (30%), followed by a native iOS app (20%). People had tried the HTML5 app and they weren't satisfied. To grow the product, company and user-base, GQueues needed native apps - simple as that. So I finally set out to build them.

Creating the native Android app was a large undertaking and some complained about the lack of other improvements during the 3 months of development.  But the clear mandate from users gave me confidence this was the right decision, and since launching the app on Google Play most users agree it was worth the wait.  Now as I embark on a similar journey developing GQueues for iOS, knowing the app will be a huge improvement for users motivates me during the long days and nights of coding.

Thursday, January 31, 2013

GQueues for Android Now Available on Google Play

The GQueues app for Android™ is now available on Google Play™!











In a survey of GQueues users last summer the number one request was the development of a native Android app, and I'm happy to finally deliver this much-awaited addition.

Android app on Google Play
Built from the ground-up, the native GQueues Android app features reliable background syncing, voice input of tasks and home-screen widgets for quick access.  With a customized layout for both phones and tablets, and compatibility with Android 2.2 and above, the GQueues app for Android provides an optimal user experience on a wide array of devices.  The 90+ users who helped beta-test the app over the last month described it as having a "fast interface, clean design and great depth of functionality." Take a tour of the app with the video tutorial below, or better yet, download it now and try it out yourself.
Read the full documentation of the GQueues app for Android here. A GQueues paid subscription is required to use the app, or you can test it out with a 2-week free trial.  All existing GQueues Lite users can test out the app with a new 2-week free trial, even if they've used a free trial in the past.

And if you don't have an Android device, not to worry, you haven't been forgotten.  Development of a native iOS app for iPhones and iPads is beginning shortly.



Android is a trademark of Google Inc. 
Google Play is a trademark of Google Inc.

Thursday, June 21, 2012

How To Get a Daily Email of GQueues Tasks

This post is part of the series, "Tips & Tricks Thursdays," which highlights ways you can take advantage of GQueues to be even more productive.

Many GQueues users have requested the ability to get a daily email of tasks that are due. Building this into GQueues is definitely on my list of improvements to make. However, in the meantime here's a trick you can use to get Google Calendar to send you these emails.

First, make sure you have activated calendar integration for your GQueues account.  
Activate Google Calendar integration
Then go to Google Calendar and choose Notifications for the GQueues calendar.
Choose notifications for GQueues calendar
Then check the box to receive an email for your daily agenda.
Select email daily agenda
Now you will receive a message every morning at 5am with the GQueues tasks that are scheduled for the current day.
Daily agenda email

Thursday, June 14, 2012

How To Create Tasks for Co-Workers via Email

This post is part of the series, "Tips & Tricks Thursdays," which highlights ways you can take advantage of GQueues to be even more productive.

GQueues of course allows you to assign tasks to others or share an entire list with someone to collaborate. However, sometimes you may want to put a task on a co-worker's queue without having it appear in your own lists or as an assigned task. Here's how to do it:

Every GQueues user is assigned a unique GQueues email address, which can be found in the Settings panel.

GQueues unique email address
You can create a task for yourself by sending an email to this address.  The subject line will be converted into the task description and the body of the email into notes.  You can use the Quick Add Syntax to set other task properties such as the date, tags and queue.

Create GQueues task via email

So if you want to allow a co-worker to create tasks in your account, just give them your unique GQueues email address (to make things fair you may want ask for their address in return!)  By adding the address to your contacts and giving it an alias you can then easily create tasks in the other person's account.
Create GQueues task via email for co-worker

Matt's Inbox with task


Tuesday, June 12, 2012

What Is Your Email Strategy?

If you're like me, you probably have a number of habits for dealing with email in your life. Some practices are intentional - tricks you've learned to keep up with the deluge of messages. Other habits, perhaps less than ideal, are formed as a result of just trying to get through the day. For most of us, email is a primary mode of communication, essential to our work and livelihood. Yet, how many of us have taken the time to think about and plan a strategy for managing email so it doesn't manage us?  As my life grows more hectic I decided it's time for me to test an intentional, strategic approach.

Emotional Inbox

Before planning a new email strategy, it's important to uncover and acknowledge the emotions surrounding our current inbox habits. My inbox evokes both excitement and guilt. I love the thrill of a new message - it gives me a small rush of adrenaline. I have a Pavlovian response to my phone's vibration and my laptop's notification popup. Many have become addicted to this titillating sequence, this instant gratification. My inbox also houses a large amount of guilt. I hold tight to the notion that I must reply to every single email, and then feel guilty when this proves impossible. When I procrastinate responding to certain emails, they linger in my inbox for months and anguish arises whenever I see them. Neither of these emotions are ideal. In fact, while the content of messages can arouse certain feelings, it seems almost silly that the tool itself affects me so deeply. Weakening the emotional hold my inbox has on me is an important goal of any new strategy I employ.

The Great Distraction

Besides eliciting unhealthy emotions, email also serves as one of the best procrastination devices in my life. Whenever I want to postpone difficult work or don't feel like focusing I can always turn to email. Checking email gives me a rush; responding to and clearing a message reduces my guilt. It's such an effective technique because I can always justify its importance. Replying to email is integral to my business and life. However, responding instantaneously is not really as crucial, but I often choose to overlook this distinction. Of course the problem is that most meaningful work requires periods of focus, as Leo Babauta so succinctly notes in his new eBook focus. So while email is important, constantly interrupting my other work is largely counterproductive. I need a better system.

Mail Processing Center

There is already a great deal of advice for strategically managing your email, and I read a number of articles to help figure out a better approach for my life. One prevalent technique which I plan to test over the next few weeks is to set specific periods for checking and dealing with email during the day, and to ignore it at all other times. While closing down email seems particularly formidable, hopefully it will help break my automatic excitement when a new message pops in, and allow me to focus on more challenging work.

Along with set email times, I have decided to not check email on my phone. When I'm away from my desk it's better that I focus on what's going on around me and the people I'm with. Logically, this new habit makes sense as well. I already have a rule that I don't respond to work emails on my phone because it's so inefficient (typing on my iPhone is slow, and I almost always need to include links and screenshots). So if I'm not going to reply, it's gratuitous to read the message once, and then mark it unread so I can read it again later on my laptop when I'm ready to deal with it.

Lastly, I plan to practice improving my decision-making skills, so I can process my inbox more efficiently. This means dealing with an email in my inbox only once. I read it and either respond or create a task if it requires more time/work later. The key is that after I've read it once, it gets cleared from my inbox, so I don't keep re-reading the same messages and feeling guilty about not responding.

I'm not really sure how this two-week testing will go, but since email is such an integral part of my life I know it's worth trying to find some better ways to manage it. What is your email strategy?



Thursday, June 7, 2012

How To Add Images to Task Notes in GQueues

This post is part of the series, "Tips & Tricks Thursdays," which highlights ways you can take advantage of GQueues to be even more productive.

Attaching files to tasks is not yet available in GQueues, though it is on the roadmap and will be developed in the coming months. However, there is a simple trick for including images with tasks which you can use right now. When typing the notes for a task, paste in the URL to an image already on the web.  This could be a publicly available image or even one stored in your Google Drive.

When you click out of the notes, a thumbnail will be appear for easy reference. Clicking the thumbnail will display the full size image at its original location.  


Note: The image URL must end with one of the following extensions: .jpg .jpeg .png .gif .bmp .webp