← IndiaThe Founder InterviewSectors    Search    Share your journey
The people who are building India’s companies · November 2026

Founder interview · App market data

Appulse Index

“Most people see the apps already at the top. I became more interested in the ones moving toward the top”

Pringal Gigaiya, founder of Appulse Index
Pringal Gigaiya, founder of Appulse Index. Photograph courtesy of Appulse Index.
In conversation with Pringal GigaiyaFounder, Appulse Index · Ahmedabad
By , Startup.Talk· 24 min read

Pringal Gigaiya grew up in Rajkot, Gujarat, and the first thing he built was a WordPress plugin. He studied Information Technology at V.V.P. Engineering College, started his career at INTUZ Solutions in Ahmedabad in 2014, and from 2016 worked remotely for companies in the US and the UK, completing an MTech in Computer Engineering at RK University along the way. After twelve years of building software for clients in India, the UK, Nigeria, Italy and the US, he decided to build something of his own.

Appulse Index is a free, live index of iPhone apps moving through Apple’s App Store top 100 charts: climbers, fallers, new releases and new number ones, across 11 countries, 25 categories and 858 charts. He built the first version alone in about a month and launched it on 29 October 2026. We spoke about why he refuses to estimate downloads, the crawler that made 31% of his traffic, and how a product started by one developer could grow into a global business.

Key takeaways

  1. Appulse Index tracks 858 App Store charts across 11 countries and 25 categories, about 30,600 apps, and collects new data every six hours.
  2. Its 0 to 100 momentum score uses only chart positions. There are no download or revenue estimates, by design.
  3. Pringal built and launched the first version alone in about a month. It is free and self-funded, with a freemium tier planned.
  4. His targets: about 10,000 monthly active users and $1,000 in monthly recurring revenue within 12 months, then 50,000 users and $5,000 within 24 months.
Part I

Before any of this

Startup.talk:Where did you grow up, and what was the first thing you built on a computer?

Gigaiya:I grew up in Rajkot, Gujarat, and I'm currently based in Ahmedabad. My journey into technology started with a simple curiosity: understanding how websites work and how I could build something of my own.

The first thing I built was a WordPress plugin. It wasn't a massive project, but it was a turning point for me. Seeing something I had written actually work on a live website gave me a sense of excitement and possibility. I realized that with code, an idea could become something real that people could use.

That curiosity eventually turned into a career spanning 12+ years in software development, working across web applications, SaaS platforms, and complex backend systems.

Today, as the founder of Appulse Index, I'm still driven by that same curiosity. The scale of what I build has changed, but the motivation hasn't: identify a problem, build a solution, and create something genuinely useful.

Looking back, that small WordPress plugin was more than my first project. It was the beginning of my journey from developer to founder.

“I realized that with code, an idea could become something real that people could use.”
Pringal Gigaiya

Startup.talk:Who or what first got you interested in software?

Gigaiya:I've always been naturally drawn to technology. Even before I started coding, I was fascinated by how software worked and how something built on a computer could solve real-world problems.

What attracted me most was the endless possibility of creating something from scratch. Unlike many other fields, software gives you the freedom to turn an idea into a working product with just a computer, curiosity, and the willingness to learn.

As I started exploring web development, that interest quickly became a passion. Every new technology I discovered made me want to learn more, experiment, and build something better.

Even after 12+ years in development, that excitement hasn't changed. Technology keeps evolving, and that's what keeps me motivated. Today, with AI transforming how we build software, I feel there's never been a more exciting time to be a developer and founder.

Part II

The road to going independent

Startup.talk:You studied Information Technology at V.V.P. Engineering College from 2010 to 2014. What did you take from those years?

Gigaiya:My years at V.V.P. Engineering College from 2010 to 2014 played an important role in shaping my technical foundation and the way I approach problem-solving today.

Beyond learning programming languages, databases, and software engineering concepts, college taught me how to think logically, break complex problems into smaller parts, and find practical solutions.

One of the biggest lessons I took from those years was that technology is a field where learning never really stops. What you learn in the classroom gives you a foundation, but real growth comes from experimenting, building projects, making mistakes, and continuously improving.

Those four years also helped me develop an independent mindset. I realized that I didn't have to wait for someone to teach me everything. With curiosity and the right resources, I could explore new technologies and build things on my own.

Looking back, college gave me more than an engineering degree. It gave me the confidence to enter the software industry in 2014 and a learning mindset that continues to guide me today, both as a developer and as the founder of Appulse Index.

Startup.talk:Your first job was at INTUZ Solutions in Ahmedabad in 2014. What did it teach you?

Gigaiya:Joining INTUZ Solutions in Ahmedabad in 2014 was my first real step into the professional software industry. It was where I started understanding the difference between writing code and building software that people actually depend on.

Working on real-world projects taught me the importance of writing clean, maintainable code, understanding client requirements, meeting deadlines, and taking responsibility for what I delivered. I also learned that being a good developer isn't just about technical skills. Communication, teamwork, and the ability to solve unexpected problems are equally important.

One of the most valuable lessons was learning to adapt. Every project came with different requirements and challenges, which pushed me to explore new technologies and think beyond a single solution.

That experience helped shape my approach to software development. Even today, after more than 12 years in the industry, I carry those early lessons with me.

INTUZ gave me something more valuable than just my first professional experience. It helped me develop the mindset of taking ownership, continuously learning, and focusing on building solutions that deliver real value. That same mindset eventually became an important part of my journey as a founder.

Startup.talk:From 2016 you worked remotely for companies in the US and the UK, including Carolina Cabinet Warehouse and The Safety Supply Company. How did that start?

Gigaiya:After gaining experience in my first job, I wanted to explore opportunities beyond my local market and work on products used by people internationally.

Around 2016, I started working remotely with companies in the US and UK. It was an important transition because remote work required a different level of ownership, communication, and independence.

Working with businesses like Carolina Cabinet Warehouse and The Safety Supply Company gave me exposure to different industries, business processes, and customer expectations. I wasn't just implementing features anymore. I was learning how software directly affects business operations, from e-commerce and inventory management to analytics and workflow automation.

One of the biggest lessons was that location doesn't limit the value you can create. What matters is understanding the problem, communicating clearly, and delivering reliable solutions.

Those experiences gave me the confidence to work independently with international teams and eventually build a product intended for a global audience.

Startup.talk:You went back for an MTech in Computer Engineering at RK University in 2020 while working. Why?

Gigaiya:By 2020, I had already spent several years working professionally in software development. I had gained practical experience building applications, solving technical challenges, and working with international clients.

But I wanted to strengthen my understanding of computer engineering beyond day-to-day development.

Pursuing an MTech while continuing to work was my way of combining academic learning with real-world experience. It gave me an opportunity to revisit technical concepts with a completely different perspective because I could connect what I was studying with problems I had already encountered professionally.

Balancing work and higher education wasn't always easy, but it reinforced the importance of discipline, time management, and continuous learning.

For me, education has never been just about earning a degree. It's about expanding the way I think and becoming better at solving increasingly complex problems.

Startup.talk:Of all the projects you have delivered, which one taught you the most?

Gigaiya:One of the most valuable learning experiences came from working on a healthcare technology platform at EVERSANA.

Healthcare systems involve complex workflows, multiple external integrations, and a high expectation of reliability. One particular challenge involved improving an insurance verification integration that initially depended on a single provider and configuration.

I worked on restructuring the integration to support multiple providers, including migrating from pVerify to Availity, while making the architecture more flexible for different API responses and configurations.

What made the project interesting wasn't just the technical implementation. It was understanding how to design software that could adapt as business requirements changed without constantly rebuilding the underlying system.

That experience reinforced an important lesson: good engineering isn't simply about making something work today. It's about building systems that remain maintainable, extensible, and reliable tomorrow.

I carry that philosophy into every project I work on, including Appulse Index.

Part III

From client work to Appulse Index

Startup.talk:After twelve years of building for clients, why build a product of your own?

Gigaiya:For more than twelve years, I've helped businesses turn their ideas into working products. I've worked across different industries, built applications from scratch, improved existing systems, and handled everything from database architecture to deployment.

Over time, I started thinking about what it would be like to apply that experience to something of my own.

Client work taught me how to build products, but I wanted to experience the complete journey of being a founder: identifying a problem, making product decisions, launching, understanding users, and continuously improving based on feedback.

Appulse Index became an opportunity to do exactly that.

I also wanted to build something that could create value beyond the hours I spent developing it. A product that could serve users globally and continue growing over time.

For me, becoming a founder wasn't about leaving development behind. It was about taking everything I'd learned as a developer and applying it to a product where I was responsible for both the technology and the direction.

Startup.talk:Why App Store charts? What was the moment you decided this was the thing to build?

Gigaiya:I've always been interested in how digital products grow, especially mobile applications. Thousands of apps compete for attention, but occasionally a relatively unknown app suddenly climbs the rankings.

I found that interesting because the App Store charts reveal changes in user attention that aren't always obvious from mainstream technology news.

Most people see the apps already at the top. I became more interested in the ones moving toward the top, especially smaller apps gaining momentum in specific countries or categories.

That led to a simple question: what if there were a place where anyone could discover these movements without manually checking hundreds of charts?

As I explored the available App Store data, I realized there was an opportunity to organize public ranking information into something useful for developers, founders, marketers, and people researching app trends.

That curiosity became Appulse Index. The idea wasn't to predict the next billion-dollar app. It was to make emerging app movements easier to discover, understand, and follow.

Startup.talk:The name comes from "appulse", the astronomy term for two objects appearing to come close in the sky. How did you land on it?

Gigaiya:I wanted a name that connected naturally with apps but also represented movement, discovery, and changing positions.

The word "appulse" caught my attention because of its astronomical meaning, when two celestial objects appear close together in the sky.

I liked the connection with what the product does. Apps are constantly moving through rankings, approaching competitors, overtaking them, or appearing alongside new names in the charts.

The word also begins with "app", which made it feel particularly appropriate for an App Store intelligence platform.

Adding "Index" made the purpose clearer: a place where these movements could be organized, tracked, and explored.

Appulse Index felt distinctive, memorable, and broad enough to grow beyond its initial feature set.

The Appulse Index banner
Appulse Index: track App Store charts, discover rising apps, spot opportunities. Image courtesy of Appulse Index.

Startup.talk:Your roles at EVERSANA and Provab ended in June 2026. Is that when you started building Appulse Index, and how long did the first version take?

Gigaiya:I started developing Appulse Index in September 2026, a few months after my roles at EVERSANA and Provab ended. The first version took approximately one month to build, and I launched it publicly in October 2026.

After spending more than twelve years developing software for different businesses, I wanted to challenge myself to build and launch a product entirely on my own.

I handled everything from product planning and UI design to backend development, database architecture, data collection, and deployment.

My initial focus was simple: collect App Store chart data, track ranking movements, and make it easier for people to discover emerging applications.

Rather than spending months building every possible feature, I wanted to launch quickly, learn from the experience, and improve the product continuously.

That approach helped me move from an idea to a publicly available product in just one month. Since launching, I've continued adding features, improving performance, and expanding what Appulse Index can offer.

Startup.talk:You design, build and run Appulse Index yourself. What does a normal day on it look like next to client work?

Gigaiya:My days usually involve switching between software engineering, product development, and understanding what the data is telling me.

I typically start by checking whether the data collection processes are running correctly, reviewing application performance, and looking for unusual movements in the App Store charts.

Then I move into development work. That could mean improving an existing feature, optimizing database queries, fixing an issue, or experimenting with a new idea.

I also spend time exploring the charts themselves. Sometimes an interesting ranking movement becomes an App Insights story or gives me an idea for a feature.

Alongside that, I manage the operational side of the product, including hosting, infrastructure, performance, and costs.

Balancing Appulse Index with client work requires prioritization. I can't build every idea immediately, so I focus on improvements that make the product more useful or more reliable.

Being a solo founder means wearing many hats, but I enjoy that. It keeps me connected to every part of the product, from the underlying code to the experience users see.

Part IV

The product

Startup.talk:Who is Appulse Index for, and what job does it do for them? Describe the user who gets the most value.

Gigaiya:Appulse Index is built for anyone who wants to understand what's happening in the mobile app market, particularly independent developers, startup founders, app marketers, product researchers, and people exploring new opportunities.

The user who gets the most value is someone who wants to discover emerging apps before they become widely recognized.

For example, an indie developer might use Appulse Index to identify rising apps in a particular category, study competing products, or explore opportunities in different countries.

Instead of manually checking App Store rankings every day, users can see which apps are climbing, which are falling, and which new releases are gaining visibility.

My goal is to make App Store discovery accessible to everyone, not just companies that can afford expensive market intelligence platforms.

Startup.talk:How do you view your positioning relative to Sensor Tower and AppFigures? Is there another competitor you think of first?

Gigaiya:I see Sensor Tower and AppFigures as established platforms serving important parts of the mobile app intelligence market. They offer extensive analytics, competitive research, and commercial intelligence.

Appulse Index approaches the market from a different starting point.

Rather than trying to provide every possible metric, I'm focused on making public App Store chart movements easy to discover and understand.

The emphasis is on momentum, emerging applications, new releases, category movements, and geographical trends.

AppFigures is probably the closer comparison because of its connection to app rankings and developer-focused analytics. However, I also think about simpler discovery tools and the App Store charts themselves as alternatives users might rely on.

My goal isn't to replicate every feature of the larger platforms. It's to create a focused, accessible product that helps users quickly answer a specific question: which apps are gaining attention right now?

Startup.talk:What is your core moat that prevents Sensor Tower, AppFigures or anyone else from replicating your feature set?

Gigaiya:I don't believe any individual feature is impossible to replicate, especially in today's world where AI has made software development faster and more accessible.

The real challenge is building a product that consistently delivers value and keeps improving.

For Appulse Index, I'm focused on three things: reliable historical chart data, a discovery experience built around ranking movements, and making that information accessible without unnecessary complexity.

Historical data becomes more useful as it accumulates. A ranking today tells you where an app stands, but its movement over weeks and months provides much more context.

I also believe being a solo founder gives me an advantage in speed. I can identify a problem, experiment with a solution, and release improvements without multiple layers of decision-making.

My long-term advantage has to come from execution, data quality, accumulated history, and understanding users better over time, rather than assuming competitors cannot build similar features.

Startup.talk:Your momentum score runs from 0 to 100 and uses only chart positions. How did you arrive at that formula?

Gigaiya:The idea behind the momentum score was to make App Store ranking movements easier to understand and compare.

When you're tracking hundreds of charts across multiple countries and categories, looking at individual ranking changes can become overwhelming. I wanted to provide a simpler way for users to identify applications showing interesting movement.

The score uses chart position data rather than estimated downloads or revenue. My intention was to keep the indicator grounded in publicly observable information instead of introducing speculative metrics.

I chose a 0 to 100 scale because it's familiar and easy to interpret, even for users without a technical background.

The score is designed as a discovery signal rather than a definitive measurement of an application's success. A high momentum score highlights an app worth investigating, but it doesn't necessarily mean the app is generating significant downloads or revenue.

I see the scoring methodology as something that can continue improving as the platform accumulates more historical data and I learn how users interpret the results.

Startup.talk:You refuse to show download or revenue estimates or to guess why an app moved. Why draw that line?

Gigaiya:Because I believe there's an important difference between what the data shows and what we assume it means.

Public App Store charts provide ranking information, but they don't reveal exact downloads, revenue, marketing spending, or the reasons behind every movement.

It's possible to create estimates, but those estimates depend on assumptions that may not be accurate, particularly for smaller apps or individual countries.

I would rather show users reliable information and clearly explain its limitations than present speculative numbers that look precise.

For example, if an app climbs 50 positions, I can show that movement. But I shouldn't automatically claim it happened because of a marketing campaign, viral video, or sudden increase in downloads without supporting evidence.

Trust is important for a data product. My approach is to separate verified observations from interpretation and give users enough context to form their own conclusions.

As the product evolves, I'm open to exploring additional metrics, but transparency about methodology and uncertainty will remain essential.

“I would rather show users reliable information and clearly explain its limitations than present speculative numbers that look precise.”
Pringal Gigaiya

Startup.talk:The indie list scores developers from public clues. How do you check that the label is right?

Gigaiya:Identifying independent developers from public information isn't always straightforward.

An app might look like an indie project but belong to a larger company, while another app might be built by a small team operating under a registered business name.

That's why I think it's important to treat publicly available signals as indicators rather than definitive proof.

The goal of the indie discovery feature is to help users find potentially independent developers, not to make absolute claims about company ownership or team size.

Where possible, the information should be checked against developer websites, publisher details, and other publicly available sources. Ambiguous cases need to be treated cautiously.

I also see developer feedback and corrections as an important part of improving accuracy.

For me, the priority is to make the feature useful while being transparent about the limitations of what public data can establish.

Startup.talk:Foldcheck lists more than 2,000 apps ready for the iPhone Duo. Why did you build it?

Gigaiya:FoldCheck came from thinking about how new hardware creates new opportunities for app developers.

Whenever a new device format or screen experience emerges, developers need to understand which applications are adapting and how those applications are using the available space.

I wanted to create a directory where people could discover apps designed for the iPhone Duo experience, including support for outer screens, larger inner displays, and split-view layouts.

For users, it provides a way to find applications that make better use of the device. For developers, it creates an opportunity to showcase their work and discover how other applications are approaching the new form factor.

It also fits the broader philosophy behind Appulse Index: helping people discover applications and opportunities that might otherwise be overlooked.

What interests me most is that a change in hardware can create an entirely new category of software opportunities, even for very small development teams.

Startup.talk:What are some of the use cases for Appulse Index that are not obvious and can add a lot of value to users? List as many as possible.

Gigaiya:Most people initially see Appulse Index as a place to check app rankings, but I believe its value goes much further.

Some of the use cases include:

1. Discovering emerging app ideas before they become mainstream.

2. Identifying smaller apps competing successfully against established brands.

3. Finding underserved categories with growing activity.

4. Studying how new applications perform after launch.

5. Tracking competitors across different countries.

6. Discovering apps that are successful in one market but less visible in another.

7. Identifying potential localization opportunities.

8. Comparing ranking movements across app categories.

9. Researching potential competitors before building a new product.

10. Finding independent developers and interesting niche applications.

11. Discovering potential acquisition or partnership candidates for further research.

12. Understanding seasonal patterns in app rankings.

13. Monitoring the impact of publicly announced product launches or updates.

14. Finding unusual ranking movements worth investigating.

15. Generating research topics for journalists, bloggers, and content creators.

16. Exploring opportunities created by new device formats through FoldCheck.

17. Building watchlists of applications worth following.

18. Identifying apps that maintain strong rankings over longer periods.

19. Discovering regional consumer preferences.

20. Learning which types of applications are attracting attention in different markets.

One of my favorite use cases is simply exploring the charts without a specific app in mind. Sometimes the most interesting opportunities are the ones you weren't originally looking for.

I want Appulse Index to become a place where developers and founders come not only to track competitors, but also to discover what they might build next.

Part V

Going live

Startup.talk:When did Appulse Index go live, and how did the first users find it?

Gigaiya:I launched Appulse Index as an independent project, initially focusing on making the core chart tracking and discovery experience available publicly.

My approach was to launch with a useful foundation and keep improving it rather than waiting until every planned feature was complete.

The early discovery strategy focused on making individual app pages, category rankings, and insights accessible through search engines. I also started sharing interesting app movements and product updates through platforms such as LinkedIn and Product Hunt.

Organic discovery is particularly important to me because every app has its own story, and people searching for those apps can potentially discover Appulse Index through the ranking information.

The initial audience is still small, but the experience has been valuable. Building the product is one challenge; helping the right people discover and return to it is another.

I'm treating this early stage as an opportunity to learn which features create the most value and where to focus next.

Startup.talk:What is the most surprising thing the charts have shown you so far?

Gigaiya:One of the most surprising things has been how quickly a very simple app can become highly visible.

For example, I recently came across DuoFridge, a $1.99 app built around a fridge-related use case that reached the top of an App Store chart.

It was a reminder that successful app ideas don't always have to be complicated. Sometimes a simple product that solves a specific problem at exactly the right moment can attract significant attention.

I've also seen regional applications perform exceptionally well in individual countries while remaining relatively unknown elsewhere.

These discoveries have changed the way I think about app opportunities.

As developers, we sometimes focus heavily on complex technology and feature-rich products. But the charts regularly remind me that timing, relevance, simplicity, and understanding a particular audience can be just as important.

That's one of the reasons I enjoy working on Appulse Index. The data constantly challenges my assumptions about what makes an app interesting.

Startup.talk:You publish a weekly report every Monday and App Insights stories. Who writes them, and how do you pick the apps?

Gigaiya:I manage the content direction myself, using Appulse Index's chart data as the starting point.

The weekly reports are designed to summarize notable movements and help readers understand what's happening across the tracked App Store charts.

For App Insights, I usually look for applications with an interesting story behind their rankings. That might be a newly released app climbing quickly, an independent developer reaching a top position, or a regional app gaining unexpected visibility.

I don't want the stories to be just another list of rankings. I try to connect the data with useful observations for developers, founders, and people interested in mobile products.

AI tools can help me organize research and prepare drafts, but the topics, editorial direction, and final review are my responsibility.

The aim is to make the data more approachable and turn interesting chart movements into stories that people can learn from.

Part VI

The hard part

Startup.talk:What has been the hardest technical problem in tracking 858 charts every day?

Gigaiya:The biggest challenge hasn't been collecting the data once. It's collecting it consistently, processing it efficiently, and making it useful over time.

Tracking hundreds of charts across countries, categories, and ranking types creates a significant amount of data. Each collection cycle needs to identify applications, update rankings, preserve historical information, and calculate movements without introducing duplicates or inconsistencies.

I built the platform using Next.js, PostgreSQL, and scheduled background processes. The collection system runs every six hours, so database efficiency and reliable processing are particularly important.

Another challenge is presenting historical data quickly. As the number of applications and ranking records grows, even relatively simple queries can become expensive if the database isn't structured properly.

Working on this has reinforced the importance of designing for scale early while avoiding unnecessary complexity.

The challenge is balancing three things: data accuracy, performance, and infrastructure cost. As a solo founder funding the product myself, I have to pay attention to all three.

Startup.talk:You posted that one crawler made 31% of the requests on a Next.js site with 30,000 pages and pushed up your Vercel bill. Was that Appulse Index, and what did you change?

Gigaiya:Yes, that experience came from Appulse Index, and it taught me an important lesson about running a data-heavy website.

The platform has thousands of publicly accessible pages, including individual app profiles and category rankings. That makes it useful for search engines, but it also attracts a significant amount of automated traffic.

At one point, I noticed that hosting usage was increasing even though actual visitor numbers weren't growing at the same rate.

After investigating the request data, I found that a single crawler was responsible for approximately 31% of requests.

The surprising part was how directly that traffic affected infrastructure costs. On usage-based hosting platforms, automated requests can consume resources just like genuine visitors.

I started reviewing caching behavior, unnecessary server work, crawler traffic, and the infrastructure costs associated with each request.

One important change was reducing excessive incremental static regeneration activity, which had contributed to unnecessary writes.

The experience also pushed me to evaluate infrastructure where costs would be more predictable.

My biggest takeaway was that building a scalable product isn't only about handling more users. It's also about controlling the resources consumed by traffic that may never become users.

Startup.talk:Everything is free, with no ads. How do you pay for it, and do you plan a paid tier?

Gigaiya:Right now, Appulse Index is self-funded. I cover the infrastructure and operating costs myself.

I wanted to make the platform accessible from the beginning because I believe useful app market information shouldn't be limited to businesses with large research budgets.

At this stage, my priority is building a reliable product, attracting the right audience, and understanding which features users find genuinely valuable.

I do plan to introduce a freemium model eventually.

The idea is to keep essential app discovery and chart information available for free while offering more advanced features for users who need deeper analysis, expanded historical data, alerts, exports, or professional research capabilities.

I don't want monetization to become a barrier to discovering useful information.

My goal is to build a sustainable business where free users continue receiving value and paying users support the development of more advanced capabilities.

For now, I'm investing in the product with a long-term perspective rather than trying to monetize every feature immediately.

Startup.talk:What is a challenging time you had building this?

Gigaiya:One of the most challenging moments was realizing that the technical cost of running Appulse Index could grow much faster than its actual audience.

As a developer, I'm comfortable solving application problems, optimizing queries, and building new features. But running my own product forced me to think differently about infrastructure expenses and long-term sustainability.

I encountered a situation where automated crawler traffic was generating millions of requests and increasing hosting costs, even though the platform was still in its early growth stage.

It was frustrating because the resources were being consumed without a corresponding increase in genuine users.

I had to investigate the traffic, understand how different hosting features were being billed, optimize the application, and reconsider the infrastructure strategy.

The experience reminded me that being a founder requires more than technical ability. You have to understand the business impact of every technical decision.

It also reinforced something I've believed throughout my career: when a problem appears, the best response is to understand its root cause and build a better solution.

Part VII

What it is all for

Startup.talk:Who believed in this before there was anything to show? What did they say or do?

Gigaiya:In the beginning, it was really just me.

Appulse Index started as a personal idea, without investors, a co-founder, or a team behind it. After spending more than twelve years building software for other businesses, I believed I had the experience and technical ability to create something of my own.

I didn't know whether the product would attract users or eventually become a successful business, but I knew I wanted to give the idea a real chance.

That belief was enough to get started.

I invested my own time, skills, and money into developing the first version. Within a month, I had turned the idea into a working product and launched it publicly.

Building something independently teaches you a lot about responsibility and persistence. There isn't always someone else to make decisions or solve problems. You have to trust your judgment, learn quickly, and keep moving forward.

For me, Appulse Index represents that willingness to take an idea seriously and act on it, even when there's no guarantee of success.

“In the beginning, it was really just me.”
Pringal Gigaiya

Startup.talk:What would make you say Appulse Index has succeeded?

Gigaiya:For me, success would mean Appulse Index becomes a genuinely useful resource that developers, founders, and product researchers return to regularly.

I would love to reach a point where someone thinking about building a mobile app naturally checks Appulse Index to understand the market, explore opportunities, and study competing applications.

Of course, building a financially sustainable business is important. I want the product to generate enough revenue to support its infrastructure, continued development, and eventually a team.

But revenue alone wouldn't define success.

If an independent developer discovers an opportunity through Appulse Index, builds something useful, and creates a successful business, that would be incredibly meaningful to me.

My long-term goal is to build something that helps other people create better products.

If Appulse Index becomes a trusted part of that journey, I'll consider it a success.

Part VIII

The road ahead

Startup.talk:Alerts are marked "coming soon". What else is next: more countries, Google Play, an API?

Gigaiya:There are several directions I want to explore, but I'm trying to approach development in stages.

One of the immediate priorities is alerts. I want users to be able to follow applications and know when something meaningful happens, such as a major ranking movement or a new chart milestone.

I'm also interested in expanding country coverage, improving historical analysis, and making it easier to compare applications across markets.

Google Play is a natural direction to explore because it would make Appulse Index useful across both major mobile ecosystems. However, that expansion depends on finding a reliable and sustainable approach to collecting and maintaining the data.

An API is another possibility, particularly for developers, researchers, and businesses that want to integrate ranking information into their own tools.

I'm also continuing to improve opportunity discovery, app insights, and the overall research experience.

My priority is to build features that solve real user problems rather than expand the product simply to increase the feature count.

Startup.talk:What are your milestones for the next 12 months, in users and revenue?

Gigaiya:Over the next 12 months, my goal is to establish Appulse Index as a useful and trusted platform for mobile app discovery and market research.

I'm aiming to reach approximately 10,000 monthly active users, with a strong focus on attracting developers, founders, and researchers who return regularly to explore chart movements and discover new opportunities.

On the revenue side, my target is to introduce a freemium model and work toward $1,000 in monthly recurring revenue.

These are ambitious targets for a self-funded product, but I believe they're achievable with consistent development, organic growth, and a clear focus on user needs.

Beyond the numbers, I want to understand which features provide the most value, improve user retention, and build a sustainable foundation for long-term growth.

My priority isn't just attracting visitors. It's creating a product that people find useful enough to return to regularly.

Startup.talk:And for the next 24 months?

Gigaiya:Within 24 months, I'd like Appulse Index to grow from an independent project into a recognized platform within the mobile app development and research community.

My target is to reach approximately 50,000 monthly active users and $5,000 in monthly recurring revenue.

By that stage, I hope to have expanded the platform's capabilities with broader market coverage, advanced analytics, personalized alerts, deeper historical insights, and additional tools for developers and businesses.

I'd also like Appulse Index to become financially self-sustaining, covering its operating costs and generating enough revenue to support continued development.

If growth supports it, I would consider bringing in a small team to accelerate product development and improve the user experience.

However, I don't want to grow simply for the sake of numbers. My focus will remain on building something useful, reliable, and accessible.

Ultimately, I'd like Appulse Index to demonstrate that a product started by one developer can grow into a sustainable global business.

Startup.talk:Where do you want Appulse Index to be in five years?

Gigaiya:In five years, I'd like Appulse Index to become a globally recognized platform for discovering mobile app trends, understanding market movements, and identifying new opportunities.

I envision a product that covers multiple app ecosystems, provides meaningful historical insights, and helps everyone from independent developers to established businesses make better-informed decisions.

I also want Appulse Index to remain approachable. Market intelligence can become complicated and expensive, but I believe there will always be room for a platform that makes useful information accessible and easy to understand.

From a business perspective, I'd like it to be profitable, sustainable, and supported by a small, highly capable team.

More importantly, I want it to have a clear identity.

When someone asks, "What's gaining momentum in the app market, and what opportunities are emerging?", I want Appulse Index to be one of the first places they think of.

That would be a meaningful achievement for something that started as a solo developer's idea.

Startup.talk:What are your hopes and fears for a post AGI world?

Gigaiya:As someone who has worked in software development for more than twelve years, I find the progress in artificial intelligence both exciting and thought-provoking.

My biggest hope is that advanced AI will make technology more accessible and allow people to solve problems that previously required enormous resources, specialized knowledge, or large teams.

We're already seeing how AI can accelerate software development. I believe future systems could make it possible for individuals and small teams to create products that once required entire organizations.

That could open up extraordinary opportunities for entrepreneurship, education, healthcare, and scientific discovery.

At the same time, I have concerns about how quickly society can adapt. Job displacement, concentration of power, misinformation, privacy, and the responsible use of increasingly capable systems are serious challenges.

I also think that as software becomes easier to create, the value of simply writing code will change. Understanding real problems, making thoughtful decisions, earning trust, and building useful experiences will become even more important.

My hope is that AI becomes a tool that expands human potential rather than replacing human purpose.

As a developer and founder, I want to keep learning, adapting, and using these technologies responsibly to build things that make a positive difference.

“My hope is that AI becomes a tool that expands human potential rather than replacing human purpose.”
Pringal Gigaiya

This interview was conducted in writing and has been edited lightly for length and clarity.

About Appulse Index

Appulse Index is a free, live index of iPhone apps moving through Apple's App Store top 100 charts: climbers, fallers, new releases and new number ones, by country and category. It covers 11 countries, 25 categories and 858 charts, about 30,600 apps, with a 0 to 100 momentum score built only from chart positions. A free account unlocks full lists, longer rank history and a 200-app watchlist. Appulse Index is built by Pringal Gigaiya in Ahmedabad, India. appulseindex.com

Appulse Index — Founder & Company Fact Sheet
AttributeVerified Detail
CompanyAppulse Index
Founder(s)Pringal Gigaiya
CountryIndia
BasedAhmedabad, India
Grew upRajkot, Gujarat
StudiedIT, V.V.P. Engineering College; MTech, RK University
Before12 years as a full-stack developer and solutions architect
FundingSelf-funded

More founder interviews

For founders

Building something? Want to share your journey?

Tell us how it started, what nearly broke it and where it is headed. We will turn it into a story like this one.

Share your journey

For readers

Want to read more human stories behind the startups?

New founder interviews and stories, as they are published.

Follow us on LinkedIn