Designing a community phonebook

We just received the first round of mockups for the community phonebook project. The initial focus is designing the profile creation process and you can see below that this is divided into two steps.

The first step is a simple data entry process where people can enter any information that they would like about themselves.

The second step allows people to specify what information they would like to share with different audiences. People will be able to drag and drop individual pieces of information to change settings or they could use the slider to move several pieces of information at once.

There is a full set of mockups (pdf warning) that also shows how you can edit individual data fields while you are on step 2 instead of needing to go back to the previous screen.

Let us know what you think about these. Does this look like an intuitive way to set up a profile and set the privacy levels? Are there things about this you don’t like or you think are missing?

If you have comments, feedback or suggestions, feel free to post here or on the Mozillians discussion group.

4 thoughts on “Designing a community phonebook

      1. I asked the question because most of the email clients I’m aware of do support some sort of LDAP, so it makes it quite simple to interface with email.

        * Setting up ldap in email clients isn’t easy.
        * I was quickly able to find LDAP to SQL bridges, but they didn’t seem to work the other way around (ie feeding LDAP data from SQL).
        * I don’t think you should run the LDAP against the one IT already maintains – it should be a different service – that would be better for speed, security et al

        Ideally I would see something like :

        A SQL powered webapp as it’s easy to setup and does all the things you want. And have a slave LDAP to that SQL db to let people wanting to interface the community address book in their email clients – ie as a read only instance.

    1. The current prototype implementation has an LDAP backend. And the current idea is hopefully that we can do the security using LDAP ACLs, so that the LDAP instance can be directly exposed and provide an alternate interface.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s