jrosen got their new app design by running a design contest:
*Guaranteed Prize* Mobile application for court location / reference information
Check out jrosen's App design contest…
Attorney & Law
This mobile application is a reference application for attorneys, paralegals and other legal professional staff. Often, these users do business at courthouses they may be unfamiliar with, as well as at those courthouses that they are familiar with but may not recall certain specific details. This application will allow the users to retrieve detailed information about specific courthouses, often in the context of supporting litigation work. Given that the user will be often using this application in support of litigation, the application will also have a few other sub-applications (features) within it, all geared to supporting their ongoing litigation work. The application goals are to enable more efficient litigation through easy access to (currently) fragmented information. Users will use this application on a weekly, and sometimes daily, basis in order to answer questions in the course of their job, and often while on the go. Wireframe sketches are available for the complex screens, but not inbox, sign-up or settings (though the elements are well documented, and should not be difficult to style). NOTE: existing website below is a company website, and does NOT have the application functionality required by this mobile application.
The mobile application may have a style of its own, but should conform to the design principles of the attached “brand bible” document. The company website and this mobile application do not need to, and probably should not, look alike. This is a mobile application and we plan for it to have its own personality. However, principles around use of negative space, button style, color, etc. in the brand bible attachment should have some place in guiding design. You are encouraged to make the application unique though, and to make it look, feel and behave like a mobile application. For each court, there are certain key pieces of information that are most interesting to users. We liken this to how weather applications aggregate the most commonly useful information into summary rows for cities, and then allow a user to drill-down to see more detail. YOU ARE MOST WELCOME AND ENCOURAGED TO USE STOCK PHOTOGRAPHY IN YOUR DESIGNS, PROVIDED THAT THE IMAGES MAY BE LICENSED FOR USE IN A MOBILE APPLICATION.
The application will have the following key screens to be designed in this contest, with multiple others to be designed as part of a follow-on project: Screen 1: Courts Screen (browsing navigation screen) 1a) County Screen (parent of Court Directory Screen) 1b) Court Directory Screen (parent of Court Detail Screen - this screen design is virtually the same as Screen 4) 1c) Court Detail Screen (child screen of Courts Directory, grandchild of County) Screen 2) Sign-up Screen Screen 3) Inbox Screen Screen 4) Favorites Screen Screen 5) Settings Screen (or Login Screen, both following same screen design) A full requirements document, which will include requirements for screens outside scope of this project, but which will better explain overall flow, will be sent individually to those that submit a design. It will not be publicly posted. The general idea: I am a lawyer and I have to file a case in a court that I am not familiar with. I would come to this application, and select "courts" from a central navigational element. This would lead me to a screen where I see all the counties listed, from there I would select the county in which the court resides. I am am now presented with a list of the courts in the county. I select the court, and see detailed information. I may favorite this court, bookmarking it for quick access later via my favorites page (where each favorite court also will show some important summary level info, before drilling down). Since this app might be available across different platforms, the first time I open it, it'll ask me to sign-up for an account. I shouldn't need to log-in often though, as the app will remember a user. Still, I'll have some settings I can change in the app, and be able to logout on the settings screen. There will also be a few other useful tools available, with the same prominence as the court information feature. One tool will be a 'reference library' where I can look up information in reference texts. The app will provide a designed/stylized table of contents to navigate to content that (initially) will be linked to on external websites for this functionality. The app will also have a date calculator, that allows a user to count the number of working days or calendar days to or from a future date. Most of the detail and complexity is in the court information and favorites screens of the application in this version. We expect most people will find and favorite a few courts, and then primarily visit the favorites page to access them, while occasionally using the other features of library and calculator. Sometimes there will be special events at the courts, such as a holiday closure, reduction in hours, or something else notable. In those cases, we would send users a message, via their inbox, to let them know something of interest was happening at a court they had favorited. The users are well educated, accustomed to accuracy and detail and always short on time to quickly get to the information they need. Streamlined workflows and the ability to get the info they want– and back to it at a later time– is important. General global application requirements are as follow- we are open to some discussion of these (see comments above about Hotel Tonight application, for example): 1. These requirements apply to all screens, unless otherwise noted 2. Upper right = Link to Messages / Inbox a. Graphical envelope i. When unread messages, shows # unread inside of a red dot (like facebook notifications) b. Upper left = One Legal logo i. Upon touch, opens in-app browser and displays http://www.onelegal.com/ c. Top center = Application name i. “Litigation Toolbox - CA” 1. Make app name a variable string, such that it can be changed in the future, and have global effect d. Bottom navigation strip has five icons, in order (left to right): i. Favorites ii. Courts iii. Library iv. Date Calc v. Settings Requirements for the contest screens are: SCREEN 1a) County Screen. This screen is the top-level browse navigation screen in the application. The *court-related* data structure goes: -County --Courts ---Courthouse Detail ----Deep detail views (eg. court fees, or rules) County Requirements: 1. This is the top-level page for Courts a. This page lists all counties (58) in California 2. Title at top = California 3. Each county is a row 4. Each row shows a count of the number of courts (courthouses) in the county (## courts) 5. Pressing a row goes to the Courthouse Screen for that county 6. Courts icon in bottom navigation strip is active (unless otherwise noted, such as in favorites selection) The county rows are expected to be a bit thinner than the rows for Screen 1b, Courts Directory. This is due to Courts Directory showing a bit more summary information, and the County page only showing the number of courts as summary level information, by row. SCREEN 1b) Courts Directory Screen. This screen will show a directory of those courts that operate in a county. Most counties will have many courthouses, but it can range from 1-30. This screen will also, with slight modifications double as a Favorites screen. 1. Title at top = County Name 2. Each row represents a courthouse in the (parent) county 3. Has a visual element for Favorite, that toggles on/off when touched and value is stored a. Star outline when not a favorite b. Gold star = favorite that has been selected c. Favorite values are stored to app and synced to user account on server 4. Each row is same style as rows in Favorites screen 5. Row data: a. Court Name b. Court Address (street, city, state, zip) 6. Courts icon in bottom navigation strip is active (unless otherwise noted, such as in favorites selection) SCREEN 1c) Court Detail Screen 1. Title at top = Courthouse Name 2. Has a visual element for Favorite, that toggles on/off when touched and value is stored a. Star outline when not a favorite b. Gold star = favorite that has been selected c. Favorite values are stored to app and synced to user account on server 3. Data: a. Court Address (street, city, state, zip) b. Website (link text) i. hyperlink to court website c. Phone Numbers (link text) i. Hyperlink to court phone directory webpage d. Court Hours i. Color or indicator(?) = green if open, red if closed e. Dropbox Info i. Will be a text string limited to about 80 characters f. Filing Deadline Schedule i. Might be different for different days of the week, should allow for different hours to be listed for each weekday, if necessary g. Small map i. On click, open in-app larger map centered on court address 4. Show back button in upper-left to return h. Link / navigation (probably designed visual navigation element) to: i. Local Court Rules ii. Fees iii. Judges iv. Departments (The above 4 items will each have a 1-3 column table of information, ideally there is a way to display this information on the court detail page, but it may be necessary to create child pages for the information.) 5. Courts icon in bottom navigation strip is active (unless otherwise noted, such as if navigated to through favorites selection) SCREEN 2) Sign-up Screen 1. Default screen after splash, if user not logged in previously 2. No global app elements 3. Required fields: a. First name b. Last name c. Email address d. Password e. Confirm password 4. After submitting form, or on same page, goes to a page that displays Terms of Service and requires user to accept a. Acceptance, date and time are stored in the user record 5. After accepting ToS, the system sends a email address confirmation email and displays a page that tells them to check their email for a confirmation email, and click the link to complete registration. a. Link to resend confirmation email i. If user attempts to login without having clicked the email confirmation link, then display page with a message directing user to check email for the confirmation email and click the link; and offer a link to resend the confirmation email. b. Link in confirmation email takes user back into the app, confirms account, and logs user in. c. No global app elements 6. Sign-up screen also shows a link (with less focus than sign up) to Log in. SCREEN 3) Inbox Screen: There should be a persistent visual element in the application, proposed for the upper-right corner, to alert people to new notifications. This is one-way messaging from the server, not user-to-user, so this inbox is really for system notifications at this time. When someone clicks the inbox element, they should go to this screen, which is the inbox. Inbox Screen 1. Title = Inbox 2. Rows = messages a. Row data i. Message Subject ii. Unread indicator (visual) b. Left swipe opens/uncovers delete button i. Delete requires confirmation by pressing delete button that was uncovered 3. No active icon in bottom navigational strip - do we show the strip anyway, or how do they get back? SCREEN 4) Favorites Screen. This is a variation of Screen 1b. The courts listed in 1b, and detailed in 1c may be Favorited. This screen has similar layout to 1b, but with additional edit elements and the ability to Share that Court's info with someone by using any of the share widgets enabled (eg. Messages, Email, Social, etc.) 1. Clickable element to add a. Goes to County Screen (with Favorites icon active) 2. Clickable element to edit a. On click, show: i. Grabable visual element to re-order ii. Delete visual element iii. Display Done link/element to exit Edit mode 3. Each row shows a specific court a. Left swipe opens/uncovers delete button i. Delete requires confirmation by pressing delete button that was uncovered b. Row data: i. Court Name ii. Filing Deadline Today: [time] iii. Filing Deadline Tomorrow: [time] 4. Favorites icon in bottom nav is active 5. Clickable element to share app with friends a. Goes to Share Screen 6. When new favorites are added, they appear at bottom of list SCREEN 5) Log-in Screen / Settings Screen. Both of these screens will follow the same screen design. The login screen will display after showing a splash screen on application launch, only if somehow a user logged out. One should rarely see the login screen; therefore the design should also be able to be used for the Settings screen, which we expect to be seen more often. This screen should be clean and simple, following the design of the rest of the application, while allowing for easy form submission with minimal (if any) scrolling. For the Settings screen, requirements: 1. Title = Settings 2. Editable text fields: a. First Name b. Last Name c. Email d. Law Firm e. Company Size f. Phone g. Change password (either a link or some functionality to change password and confirm it) For the login screen, requirements: 1. Required fields: a. email b. password 2. Button to submit: Log in 3. After a user is logged in, user is never logged out, unless manual log out. 4. No global app elements. Wireframe sketches of these screens will be posted as attachments.
What to avoid
Trying to avoid a 'library' or 'book' design motif. Shouldn't look overly 'legal' or law like: looks for more of a modern and clean design. Users will download this application knowing it is for doing their job as legal professionals, we don't need to remind them. We also don't need to make it look identical or too strongly like our own website. It should have some commonalities in principle, but it should stand on its own, and have its own design as a mobile application.
Every design category has flexible pricing for all budgets. App design starts at $849.
Full copyright with production-ready files for digital and/or print.
It all began with a design brief.
A quick, interactive guide helped them understand their design style and captured exactly what they needed in their app design.
Designers across the globe delivered design magic.
jrosen collaborated with designers to refine their ideas
When design entries come in, you can rate them so designers know what you’re looking for in your logo design.
99designs has great collaboration tools so you can pinpoint and capture your ideas
And then… they selected a winner!
Along the way, they met lots of talented designers…
We think contests are a super fun way to get design.
Recently completed contests:
We are looking to redesign an existing iOS app in the App Store. We would love to redesign this app to have a clean and
Holler@ provides the ability to monetize time with personal 1-1 video calls. After searching for a user, you can send ov
Top Attorneys in the United States - Please see brief for all details.
SSS Law helps creatives, entrepreneurs, and professionals start new businesses and scale. From drafting legal papers to