I Forced Myself to Spend a Week in Instagram Instead of Xcode
Posted4 months agoActive4 months ago
pixelpusher.clubTechstoryHigh profile
calmmixed
Debate
40/100
Indie DevelopmentMarketingSocial Media
Key topics
Indie Development
Marketing
Social Media
The author spent a week focusing on Instagram marketing for their app instead of development, sharing their experiences and insights, which sparked discussion on the challenges and ethics of social media marketing.
Snapshot generated from the HN discussion
Discussion Activity
Very active discussionFirst comment
3h
Peak period
41
3-6h
Avg / period
9.1
Comment distribution109 data points
Loading chart...
Based on 109 loaded comments
Key moments
- 01Story posted
Sep 21, 2025 at 10:00 AM EDT
4 months ago
Step 01 - 02First comment
Sep 21, 2025 at 1:02 PM EDT
3h after posting
Step 02 - 03Peak activity
41 comments in 3-6h
Hottest window of the conversation
Step 03 - 04Latest activity
Sep 23, 2025 at 11:24 AM EDT
4 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45322819Type: storyLast synced: 11/20/2025, 4:41:30 PM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
https://www.sebastienlagree.com/
Sort of like Bikram for hot yoga.
Reminds me of the inventor of the backflip, John Backflip:
https://theyardstickagency.co.uk/blog/the-strange-but-true-s...
I wonder if marketing courses also have an ethics component taught in them?
A good example of bad that can happen but damn is that just plain lazy.
More recent examples are surely more relevant and would generated more discussion.
But off the top of my head - Facebook and the genocide in Myanmar. The various collosal data breaches that usually have token punishment https://en.wikipedia.org/wiki/List_of_data_breaches
Mass surveillance and face identification by private companies for law enforcement eg https://www.auror.co/role/loss-prevention You can't appeal it and they don't respond to requests for your records (like a government department would).
Social media and addiction to it. How this should be managed with vulnerable groups, eg children?
I'm sure there are numerous better examples out there.
If I said that I coded for 15 minutes a day for a week and wasn’t impressed by the results, what would an engineer say?
Edit: I shared a couple details in my other reply under this post
It’s reassuring to know that social media posts are hard for everyone and that it isn’t supposed to be easy. I keep looking for ways to create content that is genuinely beneficial to teachers and also convinces them to try my app, but it’s hard.
You can look into https://sideshiftjobs.com or https://playkit.xyz for scaling organic posting btw (unaffiliated).
Personally I just message a lot of people directly myself and get lucky with friendly responses because creators like my apps enough that they use it themselves (edtech market makes this easier as the apps are genuinely and wholesomely bettering). Then I convince them to start new accounts focused on my app promo, in addition to less frequent commissioned promo on their main accounts.
For doing it yourself you need to get multiple devices and multiple accounts going, there are tools to help with that too. You can also post the UGC content that you pay others to produce for you, onto your own accounts. It's too difficult to consistently go viral without more frequent rolls of the dice. Focusing on a single branded account made more sense before current social media algos which don't care about your followers and won't even show it to them if the content isn't engaging enough to go viral beyond your following.
The post screenshots in those links are… uh.. hey I look forward to all of the free time everyone will have to do more productive things than “organically” shill for attention on behalf of commercial interests.
People who do UGC work get paid enough to not have to work full-time if they don't want to, giving them more time for other things in life than most jobs. Typical jobs care more about exclusivity over your entire working day than the value of your output (hence why we have more of a "laborer" market than a "labor" market), let alone sharing that value back to you as is typical with UGC contracts. It's disappointing to see that kind of elitism here.
edit:
When you pay for ads/boosted content instead, all contemporary platforms have tried hard to make the paid ads look convincingly like “organic” content for long enough for the content’s hook to land - just look at X, Reddit, TT etc.
At least with “organic” promo, established accounts have a reputation to preserve or foster when they choose what promo work aligns with their audience and their values. As a consumer I can usually evaluate how much to trust a creator too by how scrupulously they choose their promo.
With paid ads I know I am just seeing it because they were the top bidder for my attention and that the only reputation protection from the platform is to avoid particularly criminal or other extreme content.
It’s better that profits are shared than fixed. But that doesn’t change the underlying system and incentives towards dishonesty.
Paid sponsorship is fine logically but isn’t usually used to describe UGC marketing. These are accounts that are set up to promote one brand, without any existing following, and without boosting the content - leaving it to be discovered organically.
(Paid sponsorship is usually used to describe promotion through someone’s existing following and is also usually communicated within the content as being a paid ad, though not necessarily. But even with paid sponsorship, it is a form of organic marketing per the use of this term when the content is not boosted and not being used for paid ads, it simply describes how the viewer is coming across it.)
I wouldn’t use the term paid sponsorship to describe how someone creates brand-focused new accounts and posts only about the brand in order to achieve organic virality, I don’t think that clearly communicates the strategy
Others are raging about your use of the (very basic) term because it's the inverse of industry jargon. Putting it bluntly: that word you're using - organic - it doesn't mean what you think it means.
There's no elitism here, just more experienced people trying to tell you that you're making a fool of yourself.
I can expand on this but you are rudely patronizing, so goodbye to that.
> Build it and they will come is a fallacy. You have to tell people about the damn thing.
Great lesson for engineering types
But really “build it and they will come” in product development is pitched as if “they will come” because they are searching for it. Which is not really true if people don’t know your thing exists.
You might not appreciate the topic, but this is definitely not an ad, just honest learning and sharing about a difficult part of the entrepreneur job.
Here's what I've done:
- At the top of the file I've listed my audience, 3 personas
- My content has to be useful to one of those
- If I see an interesting post/take on social media I hold the link and write an idea for my own spin/take (takes 30 seconds) - log it
- If I have a problem/issue that I resolve that would be useful to my audience - log it
- If I have a key product/design/UX choice that took some time to think through - log it
- If something takes me much longer than I thought because there's more to it (iceberge effect) - log it
I've been doing this for about 6 weeks now and I've got 100 ideas for pieces of content.
One of the best pieces of advice I read is that when you're solo, many times people/community rally around you. You are the product too so you have to share what you're doing, it's interesting to many, not just your customers. They care about the advice you give, the input you have, the way you build things. You are a subject matter expert in this domain, so you should structure your content with this in mind.
"You escape competition through authenticity." - @naval
Often when I return to what I write, about 60% I look back at with the novelty gone, and reassess from a more suitable eye and cross them off the list.
Related: "Write drunk, edit sober."
Of course that's also an opportunity to combine the best of all of those iterations together, and still toss out a bunch of paper (or archive a bunch of bits.)
I think this is the dogma that holds a lot of devs back, the belief that sharing your work, the product, the thought process, the journey, the mistakes, the wins etc is “spammy”. Would save your rhetoric for those who actually spam - ai slop generators, bots, link farmers, paid shillers etc. Not indie devs on HN trying to build something for the world.
Planning out interactions according to 3 fake personas is still fake though. Not that I have any better ideas, we all have to engage with this nonsense and waste our lives producing it. It would be nice to somehow not have to.
https://www.mural.co/blog/creating-user-personas
The very idea of gaining power in the modern world is through parasocial relationships. Think Taylor Swift: her fans follow every single one of her updates even though they are highly scripted to engage exactly their "user persona", and present a Taylor who has nothing to do with the real one, another persona. Whoever can be at the top of this pyramid (i.e. make enough people believe that an Instagram-mediated relationship with a fake media persona is real) - wins the game.
I don't claim to have an answer, however, consider this. A few years ago it was considered impossible to win the battle against Big Food. They would continue to shove increasingly fake food simulacra down our throats and we'd be doomed. There was a backlash. With parasocial relationships, I feel that AI has tipped the scales into "enough is enough" category and people will demand real connection over personas.
And maybe we are just talking past each other. Maybe.
Not quite the same thing, but a perspective to be aware of...
For example, I used to be on a semi-private forum, where some people would lurk without participating, and then seemed to "arbitrage" ideas from there, to blog and social media posts, to promote their brand.
Ideas generally should be shared, and I wouldn't say that this "arbitrage" behavior is wrong, but it can sometimes seem a bit like leeching off a group without contributing.
I suppose this is more noticeable in smaller groups that are closer to "communities". Maybe no one would care if it's just more conventional social media posts where there's no community, and most people are just playing their own promotion games.
(For example, probably no one cares if someone else also forwards around the same LinkedIn inspirational leadership image post, which they themselves took from someone else. Because usually no one at all cares about those, not even the sender.)
But most of the times not a single person cares about you or your product.
That would apply more to React Native since you are stuck with its vendored abstractions and you can't just swap out React Native once you've built with it.
I think you're commenting on how iOS development is a less portable skill than a toolkit than runs on all platforms. Or that your iOS app is stuck on one platform. That is certainly true. But don't overlook the value of expertise in a native platform instead of just one set of abstractions that run on top of it. There are things you can do on the native platform, like optimizing performance, that you can't do using something like React Native.
It's all just trade-offs.
This applies to the web, too. A dev who has a good grasp of of the fundamentals (HTML, CSS, JS), the DOM, what does and doesn't trigger a repaint, etc is going to be able to take a React project a lot further than a dev who only knows how to use React.
So if they're learning the native frameworks anyway, they may as well use them. These days with Swift and Kotlin most logic code transfers pretty cleanly and most apps can be LEGO'd together from UIKit/SwiftUI/Compose components, so the workload isn't as high as one might expect.
Aside from that, early on it's usually better to start with one platform, nail the UI and interaction, and then once the app is proven worry about the other platform.
Adding more abstractions on top will not significantly improve the fact that you are at the whims and mercy of companies that don’t care about you, so I don’t see RN as an improvement.
If you want to avoid vendor lockin, don’t do mobile apps, go to web. Then, you can also just switch RN to React simply or any other framework.
With native mobile dev, lock-in is less of a problem career-wise, because it's a duopoly, so your chosen technology is unlikely to become unfashionable like it would if you were specialised in a particular web framework.
RN libraries are so often buggy and disappointing in my experience.
However, recently I decided to try something I'm calling the SaaS Schedule Sandwich.
Each month is split into four weeks:
- Week 1: Build
- Week 2: Market
- Week 3: Build
- Week 4: Video Journal
And so far it's kept me honest and not made me go live in a cave and code for a year.
I actually released the first video journal last week for our new product:
https://youtu.be/cSY-C8oiUU8
- managing your database
- creating beautiful dashboards quickly
- writing, running and sharing queries (think postman but for db)
- visually building workflows to export and manipulate your database (so underrated)
- eventually building apps directly on to your database (think retool but a desktop app)
It's an all in one, modern way to interact with your database. Desktop app.
My only suggestion is niche it down a bit. The SQL tutorial guides and features sound great, but the functional list feels a bit like a laundry list. Even here you describe it as a tool for "developers/founders/teams".
Try targeting a specific domain, tech stack, database type, or developer segment (e.g., large B2B teams, small B2B teams, indie devs, or funded startup founders) to stand out. If you pick a clear niche, you can build a stronger SEO strategy around long tail keywords and tailor both the product and the messaging and work out what order to build out features. Even if long term you plan on wanting it to be a tool for all databases, segments etc.
It's much easier to produce content with this in mind, e.g. if you were targetting getting the most out of Postgres you could easily produce a bunch of content for PostgreSQL 18 which formally came out of beta a few weeks ago and has native support for UUIDv7 etc.
Fwiw I’m doing a ton with SQLite atm as a solo dev. If your landing page had said "THE VERY BEST TOOL FOR SQLITE MANAGEMENT TO HELP SOLO DEVS AND SMALL TEAMS MAXIMIZE SQLITE PERFORMANCE AND PRODUCTIVITY" there’s a good chance I would have signed up for updates but atm it felt a little generic, some of the features I might use, some I definitely would not.
- Davinci Resolve (free)
- Epidemic Sound (for music and sound)
- ClearAudio.ai for VO processing
I then give myself the whole week to produce the video and honestly that has increased the quality by 10x. I'm not rushing it and can properly spend 2 days putting the video clips together, and another day on just the voice over alone.
If you can post fake messages today that promote your product and will start getting you users, why wait for real users to provide real testimonials that align with what you want to communicate to do the same thing 3 months from now?
Of course you want to seek out real testimonials from satisfied customers and share those as much as you can; you don't want to lock yourself in a bubble where you post how amazing your app is while emails of dissatisfied users pile up in your inbox; but it's not an OR situation, it's an AND situation.
You might also be surprised to hear that the family laughing together while drinking Coca Cola in those video ads isn't a real family, they're not really having fun, and they're not really enjoying Coca Cola for the sake of it - they're on a filming set in front of a green screen paid by the hour.
Commercials are on their face a work of fiction unless stated otherwise — for customer testimonials in commercials that are fake (in the US anyway) there has to be text saying as much. Because otherwise they’d be lying…
They are a staged conversation with a contact named "Speedometer FAQ" - not pretending like it's with a real person, or real customer testimonials.
If it makes you feel better, you could put "simulated text messages" at the bottom of such images.
It’s like saying “it’s ok to call the car ‘full self driving’ because one could figure out it’s not really full self driving.” But obviously, not everyone will realize that and you’re benefitting from the deception otherwise you wouldn’t have done it.
> Build it and they will come is a fallacy.
This is true. But is this the alternative?
No trying to minimize the efforts of people who do this as real jobs or influencing - you do you. However, generating fake message screenshot, sending unsolicited messages etc? And the winner is the one who gets the biggest rise from the consumer, authentic or not.
Distribution is hard, I get it. But isn't this the equivalent of everyone just rocking up to the village square in the most outrageous costumes and screaming into the megaphone?
You don't have to be the loudest and most outrageous if your product is great and you speak the right message to the right audience.
For the last few months, I've been monitoring all health insurance topics in some communities, and actively answering questions. It gave me a much better sense of what confuses people, down to tiny details like "I was given two documents by my insurer, and there is only one upload field in the visa application system". Another couldn't buy the insurance I recommended them because the options in a dropdown did not match his situation 1:1. No one addresses these blockers; they only cover things at a high level.
Every time I couldn't answer a question with a link to my insurance guide, I updated the guide. I rewrote some guides 2-3 times this year.
On the other end, I was in constant contact with the health insurance broker who answers questions from my readers. That's 5-6 questions per day. Again, I tried to learn from each of those.
I think you have to stay close to your users. You might notice tiny details that make a bigger difference than the superfeature you're thinking of building.
But to each their own.