Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cWTm3-0008QG-CN for pgadmin-hackers@arkaria.postgresql.org; Wed, 25 Jan 2017 20:02:31 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cWTm2-0001Hw-Vq for pgadmin-hackers@arkaria.postgresql.org; Wed, 25 Jan 2017 20:02:31 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cWTlo-00012O-BR for pgadmin-hackers@postgresql.org; Wed, 25 Jan 2017 20:02:16 +0000 Received: from mail-it0-x231.google.com ([2607:f8b0:4001:c0b::231]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1cWTlk-0007l0-0L for pgadmin-hackers@postgresql.org; Wed, 25 Jan 2017 20:02:15 +0000 Received: by mail-it0-x231.google.com with SMTP id r185so20485175ita.0 for ; Wed, 25 Jan 2017 12:02:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pivotal-io.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=MHqUCFzC9Dmn+1uUk0iDjnLOX+ymXSvwYy9ts2XUNYo=; b=MC0eR26VucbCAPGftme2kPlqBUGVhE0Q3SChSQMvw2fa8GgEjawy9nmjOihHEXDbTn UxyDlilyyo+vCBWeuUhxJycjNM7C3D3sEsrWqCreCiCFyDeERm35fIlRUeytjxx+1ZSh 0TQUFr7YF/mnCaPXW333KJOUbBgqBhfziFs3LNqsSDxDswytRpMyRgWzaoyPhbtgdHLd x/SEaGFBEU1t3N8PLI3Ai4soKAnRLPNQlQ53WCSJ4qpskqBdfZEBderBnamilO6allku YT68xvnxyS2N/eHLWPztJLv2Nzrt9zydevI/9xmnJSzDntO6r3aZe9GCR8tm21cjynfH PlNA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=MHqUCFzC9Dmn+1uUk0iDjnLOX+ymXSvwYy9ts2XUNYo=; b=i9X6d28IkVJCiPKUI+6WKzUY68jsh4PMwUMa9GGgRlyVDwMb7gMgOeThEHw158zClH hs41QWgE9KNgU+SwrZkjjrmyTeTTOelowTxxfT9fM5G3H9Xavl3UdF4WeaLeebYYawTR +Cs+ZmbybhQ531WCC+AxTpjMVAHNsuZX/YYeePrzRi0urFYhgt+R0TDuxfFD03BS1i/D 1bEcS3/cpy+S7fmXyUojluKOqnz+7j8Jwsjx66uJWeVAk6pKQhtoZz7y3s3MexxjMxbO 5OB8wqmfQ8YxiPRv7NjOnf1MgzJiooFwcysZyehQKtovmxleWqfjGoP+qib44mwenYXG s34A== X-Gm-Message-State: AIkVDXIgSLQpGC5S8JKL66fJIhOEy/T8hjM5ov/RH+1WTA2UeRZqfImqSBJm8VN4+jyRvoij/aLQL09K2oCbY4gH X-Received: by 10.36.40.142 with SMTP id h136mr4474911ith.95.1485374528042; Wed, 25 Jan 2017 12:02:08 -0800 (PST) MIME-Version: 1.0 Received: by 10.79.156.67 with HTTP; Wed, 25 Jan 2017 12:02:07 -0800 (PST) In-Reply-To: References: From: Raffi Holzer Date: Wed, 25 Jan 2017 15:02:07 -0500 Message-ID: Subject: Re: User Research Findings into PgAdmin To: Robert Eckhardt Cc: Dave Page , pgadmin-hackers , Shirley Wang , Edgar Gonzalez Content-Type: multipart/alternative; boundary=001a113f67fc1a67660546f0b5b7 X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgadmin-hackers Precedence: bulk Sender: pgadmin-hackers-owner@postgresql.org --001a113f67fc1a67660546f0b5b7 Content-Type: text/plain; charset=UTF-8 As a summary of our findings in writing: Below is a table of user needs we discovered and solutions we or the customers suggested. Some of the "missing" features people complained about are not missing at all (such as auto-complete or syntax highlighting) but the fact that people didn't know about them points to a discoverability issue we believe we can address through design. Needs Suggested Solutions Users need a reliable way to save their queries frequently Autosave, Persisting & Complete History, Persisting Un-run queries after disconnect Users need a more efficient way to type Auto-discoverable Autocomplete, Customize shortcuts, more visible syntax highlighting Users need a process to share query output with others Copy and Paste into Excel with proper formatting, Export button to MS XML Users need a way to quickly input content into pgAdmin Edit within graphic table Users need query output to be stored to reuse results Results stored in history Users need an easier way to find saved queries Workspace, Search On Wed, Jan 25, 2017 at 10:08 AM, Robert Eckhardt wrote: > My main concern is making the right decisions on what to change, and >> focussing efforts in the areas where we gain most benefit. Of course, >> the resources to do the work are also critical - the current team >> already have a good years worth of work in various additional features >> and improvements. >> > > Absolutely our concern as well which is why we don't want to work in a > vacuum. > > -- Rob > > >> >> -- >> Dave Page >> Blog: http://pgsnake.blogspot.com >> Twitter: @pgsnake >> >> EnterpriseDB UK: http://www.enterprisedb.com >> The Enterprise PostgreSQL Company >> > > -- Raffi Holzer Product Manager Pivotal Labs --001a113f67fc1a67660546f0b5b7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
As a summary of our findings in writing:=C2=A0

Below is a table of user needs we discovered and solutions we or th= e customers suggested. Some of the "missing" features people comp= lained about are not missing at all (such as auto-complete or syntax highli= ghting) but the fact that people didn't know about them points to a dis= coverability issue we believe we can address through design.
=C2= =A0<= td style=3D"vertical-align:top;border-width:1px;border-style:solid;border-c= olor:rgb(158,158,158);padding:10px">

Users need a more efficient way to type

Needs

Suggested Solutions

Users need a re= liable way to save their queries frequently

Autosave, Persisting & Complete History, Persisting Un-r= un queries after disconnect

Auto-discoverable Autocomplete, Custom= ize shortcuts, more visible syntax highlighting

Users need a process to share = query output with others

Copy= and Paste into Excel with proper formatting, Export button to MS XML

Users ne= ed a way to quickly input content into pgAdmin

Edit within graphic table

Users need query output to be s= tored to reuse results

=

<= span style=3D"font-size:18.6667px;font-family:arial;color:rgb(0,0,0);backgr= ound-color:transparent;vertical-align:baseline;white-space:pre-wrap">Result= s stored in history

Users need an easier way to find saved queries

<= /td>

Workspace, Search


On Wed, Jan 25, 2017 at 10:08 AM, Robert Eckhardt <rec= khardt@pivotal.io> wrote:
<= div dir=3D"ltr">
My main concern is making the ri= ght decisions on what to change, and
focussing efforts in the areas where we gain most benefit. Of course,
the resources to do the work are also critical - the current team
already have a good years worth of work in various additional features
and improvements.

Absolutely our= concern as well which is why we don't want to work in a vacuum.=C2=A0<= /div>

-- Rob
=C2=A0

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company




--
Ra= ffi Holzer
Product Manager
Pivotal Labs
--001a113f67fc1a67660546f0b5b7--