Laila Grainawi


Develop a voice and call recording app with seamless transcriptions, summaries and action items for your notes and meetings. 

Launch an MVP product that sets Recordkit up for tiered subscription plans, and aspects of core functionality that will allow us to expand into a per/user enterprise plan as we evolve the app in future releases to compete with other for-teams structures. 

Explored current recording apps available from native offerings to desktop-centric “for work” positioned applications to develop a lightweight (to start) app that offers an easy to use and well-designed experience from start to finish. 

We integrated a new assistant, named Kitt, to help guide the way with tooltip tutorials and intelligent AI-powered transcriptions, summaries, and action items. 

This app is currently under development and should be completed in the next month.
No stats yet.

Check back when live :)
Role: One of two designers on this project.

Title: Design Director / Senior Product Designer

Wider crew:
4 Devs
1 PM
1 Marketing

Timeline:  Approximately 3 months for design/dev of the whole app

Tooltip tutorial segmentation based on features available in each tier (Transcripts y/n)
Ah, settings. Seemingly simple, but for an MVP creates a lot of questions and answers as you work through what should and shouldn’t be included in launch. Excellent way to gut-check features and reconfirm plan tier segmentation. 
Components for plan cards. In Settings, your current plan is reflected, but also additional cards are shown based on your plan (left) for enabling easy plan switching + upsells.
Only Premium plans get Password Protection, Custom URLs, Summaries and Action items, so we had to develop interesting ways to show that they’ve found a locked feature. We looked at how other apps were handling these paywalls and feature-awareness opportunities, and created a little tile to share what’s locked (see below).
Developing Recordkit’s illustration style and motion animation for onboarding
Exploration around long presses and how users may naturally test the interface based on their mental models of other document and storage systems.
Profiles are part of 2.0 Discoverability and a wider enterprise eco-system, but it’s good to think through what foundational pieces we need at launch. For example, it’s harder to retroactively request people’s names and get them to fill in a profile, so we have included that in 1.0 onboarding flow (shown below) and settings (shown above), and 1-3 months later when we increase the app’s functionality, we’ll have it when we need it. 
Assorted profiles of mine in Settings in various apps + pin emojis to highlight useful fields and design patterns.