Complete Market Research Guide for Photo & Video Apps
Oct 30, 2026 - 1 minute read
Few app categories move as fast as photo and video. A new editing style appears on social media, and within weeks users are asking every app they own whether it can do the same thing. A competitor adds a feature that removes backgrounds in one tap, and reviews of every other app start mentioning it. Users here switch quickly and without much loyalty, because trying another editor costs them nothing but a download.
That speed is a problem for planning and an advantage for research. Users of photo and video apps write about what they want long before it shows up in download charts or revenue. They describe the effect they saw in someone else's video, the export setting they could not find, the watermark that made them leave and the app they moved to instead. A team that reads those comments systematically can see a trend forming while it is still a handful of requests.
This guide shows how a team behind a photo editor, video editor, filter, collage or AI image app can turn that feedback into real market research about its own app, its competitors and the market it serves.
Key Research Questions
Research starts with the questions it has to answer. For a photo or video app, they fall into three groups: questions about your own app and its users, questions about the alternatives users move between, and questions about how creative tools and expectations in your category are changing.
Your App
The first questions follow the user's work. What are they trying to make: a quick edit for a social post, a product photo for a small business, a family video or a polished piece for a client? Where does the app help, and where does it get in the way? Which moments do users mention when they explain a five-star review, and which when they explain a one-star review? Do complaints concentrate on editing itself, on exporting the result or on the limits of the free plan?
The second set is about requests. What are users asking for that the app does not do yet? How often does the same request appear, and is it growing? In this category, a feature request repeated by many users is often the earliest sign of where the market is going, and it deserves the same attention as a complaint.
Your Competitors
Your competitors include other apps in your category, the editing tools built into phones and social platforms, desktop software and, increasingly, AI tools that generate an image or a video from a description. What do users praise in those alternatives that yours never mention? What do they complain about that you already do well? Reviews of competing apps are as public as yours, and users in this category often name the app they came from or the one they are moving to.
The Photo and Video Market
The third group is about demand. Which effects, formats and workflows are users starting to expect? How do they feel about AI features, and where do those features help or disappoint them? How do they judge subscriptions compared with one-time purchases, and what do they expect to get for free? These questions are hard to answer from downloads and revenue alone, because those numbers show what users did, while their reasons sit in what they write.
Sources of Evidence
Evidence about a photo or video app comes from several places, and none of them has to come first. You can analyze reviews without running a survey, and you can study competitors before you have interviewed a single user. The strongest research combines what your own users tell you, what users of every app in your category write in public, and what you learn by asking.
Your Own User Feedback
Support tickets, in-app feedback, feature request forms, answers to cancellation surveys and messages from users are the most direct feedback an app has. Cancellation answers are especially useful, because they are written at the moment a user decides that the app is no longer worth paying for. Collected in one spreadsheet with columns for the date, the platform, the app version, the plan and the type of user, they become the start of a customer feedback analysis practice.
App Reviews and Creator Communities
App Store and Google Play reviews are the main public source for any photo or video app, and they cover your app and every competitor in the same detail. Reviews often name the device, the version and the exact tool that failed, which makes them useful for product decisions. YouTube adds a different kind of evidence: comments under tutorials and app comparisons, where users ask how to achieve an effect and compare tools openly. Reddit communities add longer discussions about workflows and switching, and comments on Instagram posts show how users react to new features and announcements.
Surveys and Interviews
Traditional methods still have a place. A short survey after the first export can ask what the user was trying to make and whether the app helped. A conversation with a long-term subscriber, or with someone who cancelled, shows what made the difference. Watching a user try to complete a task, such as trimming a clip or removing an object, shows friction that rarely appears in reviews. These methods belong to user experience research, and the notes they produce need the same structured analysis as reviews to become more than a set of impressions.
Researching Photo and Video Apps with Kimola
Kimola is an AI platform that turns customer feedback into enterprise-grade market research. For a photo or video app, that means taking reviews of your app and of the apps you compete with, together with comments from creator communities and your own support tickets and cancellation answers, and turning them into a structured study of what users want to make, where the app stops them and which requests are growing. The steps below follow the order a researcher would work in, and you can start with a free account, without a credit card.
Building the Dataset
After signing up, go to the Create your report area on the Home screen and paste the link to your app's page on the App Store or Google Play, or search for the app by name. With the Add Multiple option you can paste several links, one per line, and Kimola collects the reviews from all of them into a single dataset. A practical first report includes your app on both stores and three or four apps your users compare you with. The support article on creating a report by adding links walks through each screen.
For YouTube comments, Reddit threads and Instagram posts, Kimola's browser extension, Airset Generator, collects the feedback from a page and sends it to your account as an Airset, which you can turn into a report. Your own feedback can be uploaded as an .xls, .xlsx, .csv or .tsv file. If the file has columns such as platform, version, plan, user type or date, Kimola reads them, and you can filter and compare the results by those values.
By default, Kimola finds the themes in the data itself, which matters in a category where new features and effects appear faster than any fixed list could follow. If you prefer a classifier built for this kind of feedback, the Advanced option lets you choose one of Kimola's pretrained models, such as the Mobile App Feedback Classifier.
Choosing Dimensions
Dimensions are the research questions Kimola asks of every piece of feedback. You choose them when you create the report or add them later, and the guide to Dimensions explains each one. For a photo or video app, five are especially useful.
Unmet Needs belongs at the center of the research in this category. It collects what users ask for and cannot find, such as an effect they saw elsewhere, an export format, a way to edit on a tablet or better control over an AI result. Because requests in this category spread quickly, reading Unmet Needs together with the date column shows which ones are new and which are growing. Pain Points asks what goes wrong, which often covers crashes during export, lost projects, slow rendering, watermarks and features that move behind a paywall after an update.
Personas groups users by who they are, which in this category usually separates content creators who publish every day, small businesses making product photos and ads, and everyday users editing family photos and holiday videos. These groups want very different things from the same app. Experience Context shows the situation in which the app is used, such as a quick edit on a phone before posting, a longer project or work for a client. Substitutions shows what users compare the app with or switched to: another editor, a desktop program, the phone's built-in tools or an AI generator.
Reading the Report
The Overview shows the main themes in the feedback and how sentiment is distributed. Kimola finds those themes in the data itself instead of sorting comments into a fixed list of categories, so a review can be tagged with something as specific as subtitles that drift out of sync after export or skin smoothing that looks artificial.
Each review can mention several themes, and each theme gets its own sentiment. A user who loves the filters but is furious that exports are capped at a low resolution on the free plan contributes a positive mention of filters and a negative mention of export limits. A single star rating would hide that the creative tools and the business model are being judged separately.
The Performance screen ranks themes with a Satisfaction Score and a Dissatisfaction Score. These scores account for how many reviews mention a theme as well as the percentage, so a theme backed by five reviews does not outrank one backed by fifty. This protects against the most common mistake in small-scale research, which is changing the product because of a handful of strong opinions.
Signals
Signals are findings that have passed a statistical test. Kimola crosses every theme and Dimension with the columns in your dataset, such as app, store, star rating or date, and checks whether a topic is discussed more often or more negatively in one group than in the others (Differences) or more often recently than before (Trends). Only significant results become Signals, and they are ranked so the most important ones come first. The explanation of how Signals are tested covers the method in more detail.
Trends Signals are especially valuable for a photo or video app. A Trend might show that requests for a particular kind of AI editing grew over recent months across every app in the report, or that complaints about watermarks rose after a change to the free plan. In a dataset that includes the store, a Difference can show that export problems are concentrated on one platform. Signals need enough feedback and at least some selected Dimensions. When the data does not contain a pattern strong enough to report, the report shows none, which is an honest result.
Compare
Compare puts segments of a report side by side: different apps, different stores, or one-star and five-star reviews. Up to five can be compared at once, without using extra queries. In a report built with Add Multiple, the most valuable use is placing your app next to the apps your users compare you with and seeing the volume of feedback, the sentiment, the themes you share and the themes that appear for only one app. If users of a competitor keep praising how quickly it exports and yours keep complaining about rendering time, that is a decision waiting to be made.
Action Plans
Action Plans turn the findings into steps. You start by choosing or creating a Profile that describes your app, what it does and who it serves, then select a perspective: Our own offering, A rival or Our market. These match the three groups of questions at the beginning of this guide. A sensible first plan uses Our own offering with the Product Development goal, which focuses on features and the editing experience. Once your report includes competing apps, a plan with the Competitive Strategy goal focuses on how to position your app against them, and a plan with the Customer Experience goal focuses on onboarding, support and the experience of paying.
Kimola builds hypotheses from the report, tests each one against the feedback and drops the actions the evidence does not support. Each remaining action comes with a confidence level and explains why it matters, who it is for, when and where to act, the risk involved and how to see that it worked, along with the evidence behind it. A plan contains up to 12 actions. Plans work best when the report already has Signals, as the support article on how actions are built explains. Kimola's published research on a design app and on an AI video generation app shows what this kind of analysis looks like when it is applied to creative tools.
From Findings to Decisions
Research is only useful if it changes a decision. For a photo or video app the decisions are concrete, and each one connects to a specific part of the report.
Feature Roadmap
Roadmaps in this category fill up with ideas from every direction. Unmet Needs combined with Trends Signals shows which requests are growing and which have stayed flat, and Personas shows which group is asking. A request that grows among the users who pay is a strong candidate for the roadmap. A request that appears mostly among users who would never pay may still matter, but for a different reason, such as reaching new users.
Export Quality
Export is the moment the user's work leaves the app, and failures here feel worse than anywhere else. When Pain Points shows complaints about resolution, compression, frame rate, lost audio or exports that fail halfway, they deserve priority over most new features. A Difference between platforms often points to a technical cause, and Compare shows whether competing apps have the same problem.
Free Plan Limits
Watermarks, export caps and locked tools are how most apps in this category turn free users into paying ones, and they are also one of the most common reasons users leave. Pain Points shows which limits users describe as fair and which as frustrating. Substitutions shows where users go when a limit feels unfair. When a Trend shows complaints rising after a change to the free plan, the reviews usually explain exactly which part of the change users object to.
Subscriptions
Subscription complaints usually have a specific cause. When reviews concentrate on price, the issue may be value: users may not use enough of the app to justify paying every month. When they concentrate on features that used to be free, the issue is trust. Personas helps separate the two, because a content creator and someone who edits a few photos a year judge the same price very differently.
Performance
Speed is part of the creative experience. Slow previews, long rendering times, crashes on older phones and battery drain appear in reviews with great precision, often with the device named. Pain Points and Signals show whether performance problems are growing, which devices or platforms they affect and whether they appeared after a specific release.
Ongoing Research
A single report gives you a snapshot, and a photo or video app changes with every release and every new trend on social media. Repeating the research after major releases, changes to the free plan or the launch of new AI features shows whether the change moved the themes it was meant to move. Because requests in this category change quickly, repeating it every few months also shows which ideas are rising before they become obvious.
On paid plans, Feeds keep the research running continuously. A Feed collects public mentions from social media, news sites, blogs, forums, YouTube and review sites, based on the keywords and links you define. Alerts email your team when something important happens, and Mailings send a regular summary. Over time, Trends Signals show which topics are rising and which are fading.
Creative App Publishers
Larger publishers of creative apps face the same questions across several apps, platforms and markets. On the Enterprise plan, each source of feedback, such as an app, a market, a support channel or a user survey, can become a Space, a continuously growing source of feedback classified with the same Funnel, which is a shared set of custom models and Dimensions. Because every source is analyzed the same way, results stay comparable over time and between products. Spaces also calculate an NPS from what users write, on a scale from -100 to 100. It is derived from the positive and negative share of written feedback, so it is not the same as a Net Promoter Score from a 0 to 10 survey, and NPS targets can be set for each area.
When a finding needs action, Tasks assign it to the right team with the underlying feedback attached as evidence, and Tasks can be sent to Jira. After a Task is closed, Kimola measures feedback on the same topic again two and four weeks later, so a fix or a new feature can be checked against what users say afterwards. Executive summary screens give leadership a single view of what users are saying across the organization. Enterprise accounts are set up together with a dedicated Account Manager, and you can request a demo to discuss your setup.
Frequently Asked Questions
A few practical questions come up when a photo or video app team starts researching with customer feedback for the first time.
Should app reviews and YouTube comments be analyzed together?
They can be, as long as the source is kept as a column. App reviews tend to describe problems and ratings, while YouTube comments describe goals and comparisons, and one report shows both sides.
How early can a trend be seen in reviews?
Often earlier than in download or revenue data, because users ask for a feature before they leave for an app that has it. A Trends Signal confirms that a growing request is statistically meaningful and not a short burst of comments.
How many reviews do I need before the findings mean anything?
There is no fixed threshold, and the ranking on the Performance screen is designed to protect you from small samples by weighing how many reviews support each theme. Adding a few competing apps to the same report is the easiest way to reach a dataset large enough for Signals.
Getting Started
Your users, and the users of every photo and video app in your category, have already written down much of what you need to know about what they want to make and what stops them. Create a free Kimola account, add your app and a few competitors to a single report, and see which requests are growing. The guide to analyzing reviews of gaming apps and the market research guide for productivity apps apply the same approach to neighboring categories, and the market research guide for small businesses covers the method for any industry.



