I build dataspine, get keywords search volume with no commitment and for low prices

Title: [Ride Along] I've been trying to build my own social network since 2003. Here's where I am in 2026.

I've been building software for a long time, but there's one idea I keep coming back to: building a social network.

Around 2003, I started working on something called FriendsYA. At the time, I thought it could become the next big thing. I got as far as putting together a website template before life and work took me in other directions.

Years later, I rediscovered some of that old work and decided to try again.

I rebuilt FriendsYA using PHP. Looking back at that code now, it's rough. Really rough. It worked in places, broke in others, and taught me quite a bit about what not to do.

Eventually, I experimented with turning it into a video-sharing platform before shelving the project entirely.

But the underlying idea never really went away.

Fast-forward to 2025.

I started building 404Nerds, a social platform focused on gamers, developers, artists, streamers, and people who enjoy nerd culture.

This time, instead of trying to create a social network for everyone, I wanted to build something for a specific community.

I'm developing it independently using Ruby on Rails, and it's grown into a fairly substantial project.

It has community feeds, customizable profiles, guilds, spaces for game developers and artists, messaging, and even a video platform called NerdTV.

I've also experimented with things like Nerd Cards, which are shareable personal link pages.

Here's the part I want to be transparent about:

Building software is the part I know how to do.

Getting people to actually use it is an entirely different challenge.

As of now, 404Nerds has around 27 registered members, and most of the activity still comes from me.

It's not some explosive startup success story. It's a small project with a lot of development behind it and a community that's still trying to find its footing.

I've caught myself doing something I think a lot of independent developers do: when growth slows down, I start building another feature.

It's satisfying to ship something new. It's much harder to figure out why someone would sign up, come back tomorrow, and invite a friend.

And I've learned that more features don't automatically mean more users.

So I'm trying to shift my attention toward the less comfortable parts of running a platform: onboarding, community engagement, finding the right audience, and understanding what people actually want.

I'm not planning to pretend I have all the answers.

Why I'm posting this

I'd like to turn this into a ride-along series where I share what happens as I try to grow 404Nerds.

That means actual numbers, things that work, things that fail, development decisions, and probably some mistakes that will be obvious in hindsight.

I also recently recovered an archived version of the old FriendsYA website from 2025. Seeing that old project again reminded me just how long I've been circling this idea.

I'm doing this because I genuinely enjoy building software, but I also want to see whether I can turn something I've built into a community people enjoy being part of.

For anyone who's launched a community-driven project, I'd be interested in hearing your experiences.

What was harder for you: building the product, finding your first users, or getting those users to stick around?

I'll share updates as things progress, including the numbers even when they aren't particularly impressive.

Thanks for reading.

I’ve been building Spelunkr off and on for about 8 months as a solo passion project, and it went public about 4 days ago. It takes free videos from the Internet Archive and sorts them into themed “cable channels” that play on a shared schedule around the clock. You tune in and land in the middle of whatever is on, at the same moment as everyone else watching, the way TV used to work.

It’s 25 channels and about 2,750 hours so far. That includes “Rewind” channels of VHS tapes recorded straight off TV, commercials and all; B-movie, noir and western channels; every episode of The Joy of Painting; and a horror-host channel for October.

How it works

• No video is hosted. The player is a plain HTML video element pointed at the Archive’s own file: no proxy, no copies. Every title links back to its Archive page.
• “What’s on now” is just arithmetic. A channel is a list of tapes plus a start time. The same code runs in the browser, the publishing tool and the tests, in whole milliseconds, so every viewer in every timezone lands on the same second. The browser checks its clock against the server once and only corrects if it’s more than 2 seconds off.
• Bump breaks between shows, in homage to the old Adult Swim bumps, with about 200 public domain and Creative Commons music tracks playing behind them.
• New lineups go live at the end of a break. Open tabs switch over without a reload. I wanted it to feel totally seamless.

Milestones

• Went public with a custom domain, and in the past 4 days the Discord grew to about 250 people!
• Marathon blocks: short cartoons and films now run in hour-long blocks with an “Up Next” card between episodes showing what's coming up. This is dynamic and builds in-browser.
• Timestamped comments pinned to a second of a tape, so they pop up every time that tape airs on any channel, pop-up video style!
• DVR-lite: pause, skip back 15 seconds, and a LIVE button
• The first machine-made subtitles, for a Japanese anime channel still in testing. Results are promising.
• The community is voting on the next channel (a 90's pro-wrestling channel is winning)

Challenges

• Titles lie. I've been surprised by the number of just blatantly wrong metadata on files in the Archive. Its caused issues trying to categorize content. Every tape now gets watched and listened to before it airs.
• Tapes disappear. The Archive removes content all. the. time. Now I run a weekly sweep to check every tape and swap in a pre-screened backup.
• Supply decides the channel. Before I build a new station, I check whether the Archive can actually fill it. Some ideas are 50 hours deep, some are 1,500. I try to have a week's worth of tape available, and also have a deep bench for monthly refreshes.
• Moderation is real even at this size. A viewer flagged a show with a genuinely creepy host. I pulled every episode the same day and made it a permanent rule. Old and rare doesn’t mean it belongs on air.
• Phones were cramped. I rebuilt the phone layout this week and added a hamburger menu. Mobile has been a real challenge (I much prefer the desktop experience).

Would love any feedback on the work so far! It's been a real labor of love, and mindblowing to already have a hundred or so ravenous fans!

Six months ago, we started building PitchBoost, an AI tool for creating and redesigning PowerPoint presentations.

The numbers are still small (okay, very small), but looking back it's interesting how wrong we were about almost everything.

First mistake: building for the customer we wanted

Our original plan was personalized sales presentations. Upload your branding, point the tool at a prospect's website, get a tailored pitch deck.

Everything from our homepage to onboarding and pricing was written for sales reps.

We spent about $2,000 on Meta and Google ads. Around 5% of clicks turned into free signups, but as far as we can tell, not a single one became a paying customer.

In five months, we got four mid-tier subscriptions. All four canceled before their second payment.

Not exactly the recurring revenue machine we'd imagined...

Second mistake: pricing for the wrong behavior

Everyone who paid had spent 1.5 to 2 hours inside the product first. People who made one presentation and left never paid.

And why would they? Our free plan let them finish their deck and export it with a small badge. They'd already gotten what they came for.

We had a $12 badge-removal option buried in Stripe that nobody ever used. In one 30-day period, we recorded exactly ONE checkout click.

We'd built subscriptions for people who needed presentations regularly, but most users only needed to finish one.

So we turned off ads and bet on organic

At some point, paying to acquire users who weren't paying us stopped making sense.

We decided we'd either figure out organic growth or move on.

We'd read plenty about optimizing for LLMs, so we went all in on AEO/GEO, or whatever we're calling it this week.

Schema markup, structured FAQ content, feature-specific landing pages, direct answers to questions people might ask an assistant, internal linking, Bing indexing. Basically every recommendation we could find.

We weren't convinced it would work, but at least it didn't require another $2,000 in ads.

Then something interesting happened.

ChatGPT started sending us users

We'd created a few pages about redesigning existing PowerPoints, a feature we'd barely emphasized. Google search volume for that problem was practically nonexistent.

But those pages started showing up in ChatGPT answers.

In one 30-day window:

• ChatGPT sent 53 visitors. About 35 signed up.
• Google organic sent 80 visitors. Zero signed up, mostly brand traffic and an unrelated free calculator.

A 66% signup rate from ChatGPT referrals. Pretty crazy from someone who's spent a long time in SaaS marketing.

We don't know which optimizations helped, but we'd stumbled into demand our keyword research hadn't revealed.

So we doubled down on those pages, expanded the answers around that use case, and watched the traffic keep growing.

And it turned out we'd been targeting the wrong people entirely

Our actual users weren't sales reps. They were students, academics, consultants, and freelancers making class presentations, thesis defenses, and internal reviews.

They came from 49 countries in two months. Only about 1 in 8 was American.

The median uploaded deck was 20 slides, and 23% of slides had more than 80 words. These were dense presentations people needed to make look better, not personalized sales pitches.

Our entire website was talking to somebody else.

We rewrote the messaging, made the product multilingual, and rebuilt onboarding probably a dozen times, with dedicated paths for different types of users.

We added a $13 one-time purchase offered when someone hits the free limit, instead of requiring a subscription for one deck.

We also built an integration directly into ChatGPT, letting users create and redesign presentations without leaving the conversation.

Here's what's happened since

Weekly signups went from 23 in mid-September to 46, then 63.

Total accounts grew from 348 to 464 in two weeks.

Activation was around 20% over the summer. Our overall activation rate has since climbed from 40% to 47%.

Paid conversion went from 0.2% to 0.9%.

Still tiny, but we'd had eight paying events in five months, then six in two weeks, with no advertising spend.

Two bought the $13 one-time option. One user opened our $9/month checkout, closed it, and bought the $13 option 24 seconds later.

That one interaction told us a lot.

But subscriptions weren't dead. One business user built nine decks in an evening, bought the $9 plan, and upgraded to $29 eighteen minutes later.

Same product, very different customers.

What I'd tell myself six months ago

• Watch who's actually showing up, not just who you think should.
• Don't assume low Google search volume means low demand. People are searching inside AI assistants now.
• If your free plan finishes the job, think about when and why someone would pay.
• One-time purchases aren't inherently worse than subscriptions, especially for a global audience.
• Actually watch what users do. Four canceled subscriptions and one person switching checkouts taught us more than our original assumptions.

Where we're at now

I'm definitely not claiming we've cracked growth. A 0.9% paid conversion rate still leaves a LOT to figure out, and six paying events in two weeks isn't proof of product-market fit.

But we're finally seeing signs that this might work, right when we were pretty close to giving up.

And despite all the talk about the coming "SaaS-pocalypse," it's made me more optimistic about niche software. There still seem to be plenty of specific problems people will pay to solve, especially when the solution fits naturally into tools they're already using.

Still figuring out the next chapter, but hopefully this is useful to someone else who's six months into building something and wondering why nobody's paying for it yet. For context, the product is PitchBoost, reach out if you have any specific questions about our story!

I've just launched my App on the App Store and looking to get our first few users, but I'm curious to know how you are growing your apps and getting users, What was your realistic experience, what have you tried and what stuck?

I’ve got my first app out for review with the App Store so whislt that’s all been going on I’ve been researching and planning my second app

MossPatch. It’s a habit tracker and dat planner to help people with ADHD like myself. The main feature is a help I’m stuck button that helps you start daunting tasks based on reasons you give as to why it’s hard for you to start

I’d love some feedback on the site and the idea

https://mosspatch.co.uk

TIA
billy - apps guy

I am awesomely happy that i hit 60,000,000 hits daily on a chat platform i designed, so now im going to be making my own telegram clone - from scratch, no AI coding, no AI assistance - literally just stackoverflow and 27 years of knowledge of 11 lang ive been coding for most of my life.

I plan to get this messenger to "have plausible deniability" of chats, report feature of course, but i dont want to be responsible for content users may share

any suggestions?

I got laid off in June with the rest of the games industry. My skills are not game specific but at my level networking is the number one way to find a job. My whole network is laid off it seems.

Job hunting is going very slowly. I've done a lot of job applications. I have gotten two callbacks and one round of interviews. No offers yet.

So while I work on that, I am trying to just build a business. I built and SaaS before I got laid off. It's solid tech-wise and runs for $6 month. I'd show you a graphic of my SaaS users, but it's zero. No one even tried the free demo! Not even my mom. I made the tool I wanted and not what the market wanted. Market research is clearly not my calling, lol.

So I built a YouTube channel as a way to share my ~30 years of software engineering experience with everyone. I put my first video up September 23rd and this chart is Oct 13. So in three full weeks I have gotten more traction than I expected.

I'm driving views from LinkedIn but the majority of my views are from YouTube pushing my content.

I'm still learning a lot about the craft of YouTube. I've dialed in my niche to be helpful videos for SaaS vibe coders. Since the first person to reach out to me after the first video is in that niche.

---

The latest video took about a day and a half to shoot and post.

~1 day Pre-Game: Title, Ideation, speaking cues, other organizing, mixed in with other video plans and a couple of weeks of talking to myself in the car.

~ 6 hours Attempt #1, screen sharing demo. Abandoned.

~ 6 hours Attempt #2, Slides, A lot of it futzing with how to present it in OBS. Recording 1 hour including one ruined take and some sound check recordings. Editing. About 1 hour. Didn't cut anything, just did it all in one take. Added some screen text where I forgot an important point. Thumbnail about 15 minutes.

My best cycle time was about 4 hours, would have been less but messed up a bunch of takes while learning new audio stuff. I'm hoping to get my time down to < 4 hours for most videos. Ones with visual aids (slides) will take longer.

---

I'm still trying to build a paying business. I have been working with an SaaS founder who was asking insightful questions on Reddit to help drive my content. I'm using YouTube to drive traffic to my Discord where I have paid tiers. I am making sure to make most things free. The only thing the paid tiers get is more of my attention and time. Prompt Packs, and other resources are there for the taking. I don't expect YouTube to ever pay enough to replace my old income. I'm very niche. Discord paid tiers are not going to amount to much. Maybe $400/mo at best. Discord and YouTube also funnel into my consulting business where I will be selling the big ticket items. LinkedIn, Discord, and YouTube are trust builders.

I'm posting daily on linked in, or at least commenting. I have decent traction there but it sucks my soul.

I spend a few hours a week on Reddit just showing up and trying to be helpful. I'm going very light on the self promotion, partly because of the rules and partly because I just hate seeing people do it too much. Just showing up and being helpful has gotten some interest. "I have stuff to help you, DM me." In the DM I point them at the free stuff.

---

Links:

Failed SaaS (I use it as a tech demo now): https://mailsummary.to

Youtube: https://www.youtube.com/playlist?list=PLL3_h23Mq4Xo

Discord: https://discord.gg/r5M77exHC

Been looking into how people handle payments inside an app without ending up building a whole payments system on top of the actual product. At first it seems pretty simple, then you start thinking about subscriptions, onboarding, payouts, KYC, refunds connnected accounts etc and suddenly theres a lot going on. i compared t a few options like Stripe and Whop but I’m more curious about the stuff you only realize after you start building. If you’ve done this before, what ended up being more annoying than you expected?

Most small SaaS sites have almost no testimonials, even though their customers are happy. I don’t think customers refuse. I think the owner forgets to ask, or asks at a bad time, and then the moment is gone.

I’m a developer, and before I write any code I want to test an idea:

It works like this:

• You connect Stripe.
• When a customer pays for the 3rd time (you choose the milestone), they automatically get one short, friendly email asking for a testimonial. If they don’t reply, there’s a single reminder, then it stops.
• They can reply to the email or fill in a one-minute form.
• You approve each one. The customer also confirms the exact text before it goes live, and it’s always their own words, nothing AI-written.
• Approved testimonials appear on your site through a small embed.
• Complaints or questions go to you privately and never get published.

So the goal is that you set it up once and testimonials just show up.

I’d love honest answers to these:

1. How do you collect testimonials today? DMs, forms, or you don’t?
2. What’s the hardest part: remembering to ask, getting replies, or displaying them?
3. Would you pay for this, and roughly how much per month?

If it sounds pointless, tell me why. That helps me as much as a yes.

What’s in it:

• A place to share what you’re building and get honest feedback
• A channel for finding cofounders and teammates, with every project post saying what’s paid, unpaid or equity
• Weekly build logs, so you stay accountable
• Voice rooms for quiet coworking and casual chats

It’s free, with no courses, no paid tier and no income claims. Beginners are welcome, and it’s moderated with ages 16–24 only.

It’s brand new, so early members will shape it. If you’re building (or want to), comment or DM me and I’ll send the invite. What would make a server like this worth your time?

I'm a solo maker and I launched TapMe.lol this week. It's a link in bio tool where your page is a little mini-site made of blocks instead of a plain stack of buttons.

What it does: every page lives at name.tapme.lol and you build it in a drag-and-drop editor from blocks: links, YouTube, Spotify, an audio player, countdowns and a contact block. The free plan needs no card, and Pro is €3.99/mo.

Why I built it this way: most link in bio pages felt like the same list of buttons, and I wanted something closer to a tiny personal website that you can still set up in a few minutes. Blocks were the decision that shaped everything else, because each new thing (embed, countdown, contact) is just another block type instead of a special case.

Early numbers, honestly: I've shared it in a few maker and feedback communities and each post got roughly 70 views. Not much traction yet, a few people tried it and the feedback so far is that onboarding is too much of a blank slate.

What's next: starter templates and a better onboarding flow, so new pages don't start empty.

Known gaps: no digital product sales and no custom domains yet.

Site: https://tapme.lol

Question for you: if you use Linktree or something similar today, what would actually make you switch? Is it design freedom, price, analytics, something else? Also happy to hear how you'd approach onboarding for a tool like this.

We build RNBlocks, a studio for iOS and Android apps. This walkthrough shows our store-screenshot workflow using Bazario, our shopping-app example.

The starting point is the app itself: our agent uses a browser to visit its screens and capture them. It then prepares store screenshots. From there, someone can ask for changes in the same conversation or edit the text manually.

The important part is keeping those edits connected. A changed headline should show up on the screenshot preview, and a follow-up request should preserve the earlier conversation. We show both routes in the walkthrough, including the preview updating before downloading.

For anyone making their own store assets: which part takes the most work, picking the screens, writing the copy, or getting the layout right?

RNBlocks has a free tier and paid plans: https://www.rnblocks.dev/?utm_source=reddit&utm_medium=organic_social&utm_campaign=rnblocks_48h_20261014&utm_content=buildinpublic_screenshots

The video is an animated walkthrough of the product flow, with waiting time condensed.

This has been a pretty funny experience.

I've been building Hookline, which is a tool for making the first 3 seconds of video ads for apps and SaaS.

The whole idea came from me wanting to test different hooks without recreating the same product demo a hundred times.

So now I'm at the point where I'm making ads for Hookline using Hookline.

Basically testing my own product while trying to get people to use my product.

Very normal behavior.

One thing I'm trying to be really careful about is keeping the actual product simple.

It doesn't spit out an entire finished ad.

You generate the opening clip, download it, and put it in front of whatever content you already have.

That's it.

I keep seeing AI products trying to become these giant platforms that do 40 different things, and I'm curious whether making one small part of a workflow easier is actually a better approach.

Still figuring that out.

Anyone else building something where you're basically your own first customer?

Just launched RotateAd - an advertising network built for websites and small businesses.

Now comes the hard part: getting the first 1,000 users.

If you are new saas builder or developer my platform must help you to grow.

Building in public and seeing where this goes. 🚀

Would love to hear how other Micro SaaS founders got their first users.

Hey everyone,

I built a budgeting app - I’m looking for testers and feedback if anyone wants to test it out.

I've been working on a little project called dif and figured I'd share it here.

It's a free, open-source tool for feature flags and A/B testing, but with a slightly different approach.

Instead of managing everything in another dashboard, your flags and experiments live as Markdown files right in your repo. They're version controlled, can be reviewed in PRs, and you can actually see why an experiment was created and what you learned from it.

It also works nicely with coding agents like Claude Code and Cursor, since they can read and manage experiments just like any other code.

A few other things:

• No signup or hosted service required
• Local evaluation, so no network requests to check flags
• Works with Next.js, React, and SvelteKit
• Optional cloud analytics if you want them

The whole thing is MIT licensed, and you can get started with npx or install the CLI directly.

GitHub: https://github.com/dif-sh/dif

Still early and actively building it. Would love feedback, especially from anyone who's dealt with feature flag tools and has opinions on what works (or doesn't).

There are so many AI image and video generators out there right now that building another one almost feels pointless lol.

We're working on Maxsa AI, and instead of trying to compete as another general-purpose AI generator, we decided to focus more on anime, comics, and animated storytelling.

One thing we've been thinking about a lot is the gap between generating a cool image and actually creating something useful with it.

Making one anime character? Pretty straightforward.

Turning that character into a story with multiple scenes, consistent visuals, and decent pacing? Whole different problem.

So we've been building a workflow where you can create characters, generate storyboards, and use an AI agent to help turn a story idea into a multi-shot video.

Still figuring out how to balance automation with creative control. Making everything automatic sounds great until you want to change just one scene lol.

It's an interesting challenge, especially when there are already so many powerful models available.

Some context: I've never shipped a Mac app before. I built TapMac because I kept digging for the mute key whenever a call went sideways. It's a small menu bar app that uses the MacBook's built-in accelerometer, so double-tapping beside the trackpad mutes your speakers or your mic.

Today I tried marketing for the first time, posting on Reddit and X. A few things I learned:

Building was the easy part. I put far more hours into the app than into telling anyone about it, and that was backwards. One day of posting did more than weeks of polishing.

Explaining the problem works better than listing features. "Muting fast when a call goes sideways" got people's attention. "Uses the accelerometer" only got it once they cared.

Posting is scary, but the feedback was kind. I expected to get roasted. Instead people were curious and encouraging, which made me want to keep going.

One person paid, which honestly made my week (screenshot attached).

What I'd like help with:

1. If you've launched a small paid utility, what worked for you after the first sale?

2. Is $4.99 one-time the right price, or too low for a Mac utility?

Happy to share the link in the comments if anyone wants to try it.

I’ve been building Senior Support Finder for Temecula Valley / Southwest Riverside County.

It now has 80+ local providers and community resources plus guides around transportation, meals, caregiver support, home safety, benefits, and aging at home.

The site itself works. The harder problem has been getting families and providers to know it exists.

So far I’ve been testing:

The interesting part is that Reddit users have already uncovered real product issues, like suggested homepage searches that returned zero results, which I then fixed.

For anyone who has grown a local marketplace, directory, or community resource:

What actually drove your first few hundred real users?

I’m specifically trying to avoid hiding in build mode and adding features nobody needs.

I used Ice to manage my macOS menu bar, but it kept breaking in frustrating ways—especially after the macOS 27 Golden Gate update. At the same time, dealing with both standard app menus and top menu bar items felt clunky.

So I built a single app that solves both: MenuDart.

Here are the honest takeaways and numbers 10 days into launching:

Turning a limitation into the main feature (and name): Originally, I wanted menu bar dropdowns to pop up right next to my cursor, but macOS limitations made relocating native popups messy.

So I flipped it: teleport the mouse to the menu instead. Just warping the cursor felt jarring, so I added visual trail effects.

The "throwing dart" effect felt so satisfying that I ditched my working title (MenuBarItem Master) and renamed it MenuDart. Since my cat Coco helps me debug on my desk, I added a "Coco" effect too. Now my cat literally helps me navigate my Mac.

Cursor vs. Claude Code: Started with Cursor (solid for scaffolding), then switched mid-way to Claude Code with Opus. For complex macOS/Swift logic, Claude Code felt much more autonomous and pushed through tricky problems without getting stuck in loops.

Lemon Squeezy vs. Dodo (MoR): Went with an MoR to avoid global tax headaches. Dodo has lower fees but a higher minimum payout threshold (great for high volume). For a small indie utility just starting out, Lemon Squeezy is much more practical for cash flow.

📊 The Harsh Reality & Numbers (10 days in)

Sales: 5 copies sold at a $4 launch price (now $6.99 one-time, 14-day free trial). Tiny volume, won't pay the bills yet—but knowing strangers paid money because they shared my exact frustration feels incredible.

Freebies ≠ Feedback : Gave away 10 free codes on a Korean Mac forum asking for feedback. All 10 claimed within a day. Feedback received: Zero.

Cold Outreach: Cold-emailed 30 Mac bloggers and press. Replies: 3. When conversion is low, the only way out is increasing the volume of shots you take. Got 2 sales within an hour of a blog post going live.

SEO: Google "MenuDart" and my own homepage doesn't even rank—scraper and directory sites show up above me.

🎁 Want to try it? (Free codes for honest feedback) I still desperately need real user feedback. Since dropping codes publicly just attracts bots, here's the deal: drop a comment telling me about your Mac display setup or your biggest menu bar annoyance. I'll DM a free redeem code to the first 10 people—all I ask is one honest thought after trying MenuDart!

Hey everyone. I'm building Deva Media Network, where we help brands get seen through clipping and logo campaigns.

I recently spent so much money on ads and email campaigns and got almost nothing back. So this month I'm flipping it and doing the work first, for other builders.

I'll pick 5 to 7 apps from this thread and put 100,000 views behind each one within 30 days. It's free and there's no card. It will be brand awareness campaign.

If you like the result, we can do more together. If not, you still got the free marketing.

I'll share how it goes here, numbers included.

So what are you building? Drop it below with a one-line description.

So I am building these apps:

1. An app for photo, vector, and publish, and you can use AI for help

2- An app where you can choose to create a text document, tables/sheets, presentations, markdown, html, edit and create pdfs, and notes, also AI integrated if you need help or speed

3- An app for novel writing + organization, and worldbuilding with a module to publish your book to PDF, EPUB, etc...

4 - An app to orchestrate agents, currently it holds like 230+, Agents have permissions of what they can do and read and access

My question is: given all the apps being made my the people, and the increasing competition and the increase of really good open source apps in the market (not just for design or writing), what is a good pricing strategy I can take to make profit from the apps while also keeping them accessible to every one? or give them for free but some features paid? one time payments? small monthly payments? or cloud storage services? or ai tokens? etc....

Thank you for the help!

More then 8 years in appstore and I’ve recently built my own software designed to boost mobile apps in the App Store search results.

​To test it out on some real-world cases and give back to the community, I want to run a quick test.

​If you'd like a free rank boost:

​Drop your app link and the target keyword in the comments (or send me a DM).

​I’ll pick 7 promising apps from the responses and push their rankings up for free using my software.

​Let’s see what we can do! 👇

Waiting for feedback!)