top of page
Revamping Dailyhunt's Product Vision
🚀 Sprint-based revamp to shift the product vision and provide end users a seamless news reading experience.

🎯Resulted in a x.xx% increase in Monthly Active Users
My Roles & Responsibilities
Research, UI Design, Testing, Prototyping

Updating the Design System

Co-ordinating with Developers and PMs

Pitching to Stakeholders
One of the multiple design sprints
during my role at Dailyhunt

Team: Me, Sreekanth, Sachin (Product Designers) + Manager + PMs + Developers
Figma, Google Docs, Google Sheets
ℹ️ What is Dailyhunt?
Dailyhunt is an Indian content and news aggregator application that provides local language content in 14 Indian languages from multiple content providers.
It is
one of the top 10 consumer applications in India with 283 million MAU (as of June 2021)
🤔 A bit of back story....
Dailyhunt’s previous huge release was DH Social - where they aimed to make the news reading platform more community-based, introducing social elements like resharing, engagement bar, groups, and more.
DH social did not perform according to the intended metrics. Disparate features and experiments competed for focus. App reliability and performance issues increased exponentially. There was a drop in Monthly Active Users as well as time spent on the app.
Dailyhunt’s vision shifted. The new goal was to focus on the news reading experience. Inform & Enrich its readers rather than entertainment.
image 28.png
image 30.png
DH Social Playstore Screens (2020)
The Problem
How do we measure success for this new vision?
Since it was a fast sprint, we needed to have some metrics in mind to make sure the design was successful.
Group 74.png
Retention rate over CTR.
Focus on More Long Term Users
Group 74.png
Increase and Stickiness in DAU/MAU.
Get people to come back to the app more often 
👁 The focus for this particular sprint was the Detail Page.
The vision revamp was done in two main sprints - The Feed Card Design & The Detail Page Design.
Detail Page Sprint
(14 days)
Feed Card Sprint (10 days)
Feed Card Sprint
Redesigning the news feed cards on the home page that people scroll through
Old Design
New Design
Group 12141889 (3).png
Detail Page Sprint
Redesigning the news detail page that people land on to read the news story, after clicking on the feed card
Old Design
New Design
Group 12141890 (2).png
Revamping the Detail Page
Screen Shot 2023-03-30 at 4.53.32 PM.png
We constantly converged and diverged as a team throughout the process
Process (1).png
Insights from User Research
Author of an article is important
Profiles shown in likes carousel not useful - not needed
Priority of what people notice first: 
Image > title > meta > description > publisher > comments > related
Too much scrolling to read full news 
    Opportunities and suggestions :
  • News Summary
  • Highlight important Words
  • Top nav bar taking too much space
People don’t repost 
"no use of reposting on the platform as friends use Whatsapp to share"
People confused by the impact of ‘liking’ a news story
  • People think it means ‘show more of.’  
  • 1 user thought will have an impact on other people’s feed
Users didn’t know you could horizontally swipe to see the next story
Re-educate if the user has never swiped
Users don't know that the save feature exists
     Opportunities and suggestions :
  • Good to have 
  • Asked for an upfront save option
Competitor Analaysis
Looked at competitors across the Indian, Chinese, Global, and Aggregator landscape, and noted down patterns and observations of what I found useful, interesting, or unique. Some patterns focused on were Ad placements, navigation to view the next news story, comments and related stories.
Screen Shot 2022-06-30 at 3.01.59 PM.png
Some interesting Data Points:
Collaborated with our Data Analyst and PMs to analyze how readers were getting around and the possible reasons for the recent decline in key metrics.
Most popular features
  • Comments Tab                  (30% click rate😱)
  • Related Stories
  • Swipe to the next story
Least popular features
  • Reply clicked
  • Repost
  • Profile in Like Carousel     (0.0039% click rate 🤕)
In the 3 dot menu in top bar
Most popular features
  • Share
  • Save
  • Show Less
Least popular feature
  • Report                (0.0009% click rate 🤕)
After prioritizing according to the insights gathered, we decided on the order of elements:
1. Back | 3 dots | Save Story
2. Image
3. Title
4. Meta (Publisher)
5. Description : p0 ad :
6. Publisher Logo
7. Hashtags
9. Like
10. Related Stories
11. Like | Share | Comment | Repost
Need to show an ad in the first fold
👉 How can we incorporate ads without ruining the reading experience?
Multiple Iterations.
Screen Shot 2023-03-30 at 6.34.44 PM.png
Stitching the final design together with the
Dailyhunt Design System
Using components already present - The Design System consisted of 2 subsystems with their components each:
  • Android
  • iOS
Creating new components and adding them to the Design System
Main Changes
Top Navigation Bar
Old Design
Screen Shot 2022-07-31 at 3.53.14 PM.png
New Design
Screen Shot 2022-07-31 at 3.53.22 PM.png
Quick Navigation to comments 

Comments were the feature with the highest engagement and click rate (through data)
Save Story upfront 

Experiment to see if people use the feature more. Research gathered that people wanted to save stories but didn’t know the option already existed on the app.
Comments Section
Old Design
New Design
Screen Shot 2022-07-31 at 3.43.55 PM.png
The tabs under 'Discussions'

The reposts tab was barely clicked on, and comments had the highest click rate, eliminating the need for the repost tab.
Brought comments out, took out reposts
Screen Shot 2022-07-31 at 3.44.09 PM.png
Reactions Carousel
Old Design
Screen Shot 2022-06-22 at 10.57 1.png
Showing profiles in the like carousel

Very few people clicked (through data) + users said it was not useful
The like button & only kept the emotions

People were getting confused about the purpose of the like button, thinking it was adding to their algorithm                    
New Design
Screen Shot 2022-06-22 at 10.57 2.png
Visually showing the aggregation of emotions  

To give readers an idea of how different people are reacting to a news story and urge them to contribute as well.
Final Design
Old Design
New Design
Screen Shot 2022-07-31 at 4.52.02 PM.png
Screen Shot 2022-07-31 at 4.52.27 PM.png
Screen Shot 2022-07-31 at 4.52.36 PM.png
Screen Shot 2022-07-31 at 4.52.15 PM.png
Screen Shot 2022-07-31 at 4.52.02 PM.png
🤝 Keeping in mind dev and business constraints.
Old Design
New Design
Group 3260.png
The New Design
SAVES 84 pixels extra in (Image+Title+Source & meta)
ADDS 137 pixels extra to Ad visibility
For best and worst-case scenarios.
Scenario: Screen Sizes
Group 3261.png
worst case - 4.7 inch
average - 6 inch
best case - 6.5 inch
Scenario: Title Cases
Worst Case - 4.7 inch

2 lines (8 words)

6 lines (22 words)

Best Case - 6.5 inch

2 lines (8 words)

6 lines (22 words)

Group 3262.png
For all Languages.
Dailyhunt supports a total of 14 different local languages. So our design needed to work for all languages.
Scenario: Malayalam - the language with the longest words
Worst Case - 4.7 inch

2 lines (6 words)

6 lines (15 words)

Group 3263.png
Best Case - 6.5 inch

2 lines (6 words)

6 lines (15 words)

Group 3263.png
For all Screen Sizes.
Screen Shot 2022-06-22 at 11.10 1.png
👁‍🗨 Usability Testing
Reaching out to our previous interviewees.
Screen Shot 2022-06-22 at 11.56 1.png
Observational Testing
Screen Shot 2022-06-22 at 11.57 1.png
Group 3264.png
Before Testing
Galaxy Note9 Mockup-1.png
After Testing - Live Screens
Galaxy Note9 Mockup.png
iPhone 13 Mockup.png
🏆 Result
Group 74.png
MAU increased by 6.5%
Group 74.png
Avg time spent increased from 5 minutes to 13 minutes
💭 Takeaways
Fast thinking and decision-making. Since it was a quick sprint, I was pushed to make quick decisions and learned how to make decisions based on the data available to me as well as intuition.

Power of diverging as a team and then coming together to share our thoughts. To save time, we divided the work and created our designs and iterations for each feature. We then came together to share our ideas. This opened up ideas that one or the other of us would've never come up with before.

Collaborating with multiple teams. I had to constantly coordinate between Developers and PMs for data asks and to make sure my design was feasible.

Balancing business and user needs. The revamp pushed me to brainstorm ways in which we could incorporate the business needs while not taking away from a smooth experience.

Pitching to Higher-up and Stakeholders. Learned to pitch my designs and decisions to stakeholders and show them the best and worst cases while incorporating business needs.

View previous

View next

bottom of page