Hey, glad you’re here
So you found this page. That’s awesome.
Look, here’s what’s actually going on. We started Techies Times because the apps space is moving insanely fast, and most people can’t keep up. Everyone’s building apps, everyone’s using apps, but very few people actually talk about what makes a good app, what apps are worth your time, and how to actually build this stuff well.
Our readers? They’re developers, tech enthusiasts, people trying to find the right apps for their workflow, and folks curious about how technology actually works. They want to know which apps are actually useful versus the ones that are just pretty interfaces with no substance. They want to understand app development from people who actually build this stuff. They’re looking for honest takes from people who know what they’re doing.
If you know apps—whether that’s building them, reviewing them, or understanding the ecosystem—and you can explain it in a real way without the tech jargon overload, we want you writing here. Whether you’re an app developer, a UX designer, a product manager, or you’ve just spent years testing apps and learning what works, there’s definitely space for you.
This isn’t about promoting app stores or getting people to download random stuff. It’s about actual apps that solve real problems.
Who we’re looking for
Real talk? We’re selective, but not in a snobby way. We just need people who actually know their stuff.
If you fit any of these, we’d love to hear from you:
-
App developers and engineers – You actually build apps and understand the technical side
-
UX/UI designers – You know what makes apps usable and beautiful
-
Product managers – You’ve shipped apps and know the full lifecycle
-
App reviewers and tech writers – You test apps and know what matters
-
Growth marketers – You’ve scaled apps and understand user acquisition
-
Indie app developers – You’ve built and launched your own apps
-
App analytics experts – You know how to read data and understand user behavior
-
Anyone seriously studying apps – And can back it up with real knowledge, not just hunches
You don’t need some fancy tech degree (though they help). Some of the best app knowledge comes from people who’ve just built stuff, failed, learned, and built better. What matters is that you genuinely know this stuff. Like, really know it. We can tell when someone’s just copying app store descriptions, and so can our readers.
Topics we’re genuinely hungry for
Look, I could list forever, but here’s what would actually resonate with Techies Times readers:
-
Best apps for productivity and work – Apps that actually move the needle
-
Coding and programming apps – Learning to code, development tools, platforms
-
Apps for gaming – The ones that actually deliver on what they promise
-
Email and communication apps – Beyond the basics
-
Privacy and security apps – What you actually need vs what’s overkill
-
Data storage and backup apps – Safe and practical solutions
-
App development tutorials – Building your first app, frameworks, languages
-
Native vs cross-platform apps – The real differences that matter
-
App design principles – What makes apps good or terrible
-
Mobile app trends and future – What’s actually coming next
-
App monetization strategies – How developers actually make money
-
Performance optimization for apps – Making apps faster and less bloated
-
App store strategy and ASO – Getting your app discovered
-
Real reviews and comparisons – App A vs App B with actual details
-
Budget apps that work – Quality without the price tag
If you’ve got an angle that actually helps people build, use, or understand apps better, pitch it. We’re not going to be difficult about it.
What we actually need from your article
Alright, so here’s what makes an article work for Techies Times:
Length: Aim for somewhere around 1,500 to 2,500 words. Shorter guides or quick reviews? 1,000–1,200 is totally fine. Just don’t pad it with garbage to hit numbers. That’s annoying.
Talk like a real person: Write like you’re explaining apps to a colleague. Short sentences. Normal paragraphs. No developer jargon overload. If you use a technical term, explain what it actually means. Not everyone’s a programmer.
Keep it original: Your article has to be actually yours. Avoid copying from app store listings, tech blogs, or stealing development tutorials. We want what’s in your brain. Your experience. Your real perspective.
Back your claims up: If you’re saying something about apps works or matters, show why. Use real examples, screenshots, your own testing, whatever. Just be honest about how you know what you know. Our readers appreciate transparency.
Make it readable: Use headings so people can skim it. Start with something that hooks them. End with actual action steps they can take. Don’t bury the good stuff in the middle.
Keywords should feel natural: Use “apps” in your intro, in a heading or two, and somewhere near the end. But don’t force it. If it feels weird, it IS weird.
Link to our other stuff: When it makes sense, link to other Techies Times posts. Talking about learning programming? Maybe reference How to Learn Coding at Home. Discussing gadgets? Link to posts about Mini Gadgets or gaming earbuds. Discussing data security? Connect to tech topics. Helps readers find more and helps us too.
Give us your SEO title and description: Tell us what you’d call it in Google (under 60 characters) and write something short that makes people click (under 155 characters).
How to format your article
I know formatting sounds boring, but it actually matters when people are reading on their phones:
Headings: Use H2 and H3. That’s it. Don’t go deeper. People need clear markers to know what section they’re in.
Keep paragraphs short: 2–4 sentences max. Long paragraphs just don’t work. People read on mobile now.
Use lists: Bullets for features, tips, or lists. Numbers for step-by-step processes. People love lists. Easy to scan.
Bold the important stuff: If there’s something people really need to remember, bold it. Just don’t overdo it.
Use screenshots and visuals: Got screenshots of apps you’re reviewing? Development screenshots? Include them. Make it visual. People learn better with pictures.
Real examples help: Talk about actual apps you’ve used or built. Tell what worked, what didn’t. Way more interesting than theory.
The link rules (keeping it honest)
Here’s the deal:
Our articles: YES. Link to other Techies Times posts when relevant. Helps readers explore and helps us.
Legit tech and app resources: YES. Official developer docs, app stores, trusted tech resources, research sites.
Your own apps or services: NO. Don’t link to your app in the app store or your development course. We can tell.
Affiliate links: NO. No commissions disguised as helpful app advice. People see through it.
Promotional spam: NO. Random links to random apps you don’t actually use? Nope.
Your website in your bio: YES. One link. Keep it professional and relevant.
Simple rule: If this link actually helps the person reading understand or use apps better, include it. If it’s just promotional? Don’t do it.
Write us your author bio
At the end of your article, include a short bio about yourself. Keep it real. 50–100 words. Tell us:
-
Your name and what you actually do with apps
-
Your experience building, designing, or reviewing apps
-
What you specialize in or what you’re known for
-
Where people can find you online
Here’s an example:
Alex is a full-stack app developer who’s built and launched like 6 different apps over the past 5 years. They’ve worked on iOS, Android, and web apps and know the quirks of each platform. They’re obsessed with making apps that actually solve problems instead of just looking pretty. They share real development lessons and app reviews. Find them on GitHub or their tech blog.
How to actually submit your article
You wrote something solid. Now what?
Step 1: Email us your pitch first. Don’t send the whole article yet. Subject line: “Guest Article Pitch – Apps”
Tell us what the article’s about (few bullet points), why our readers would care, and why you’re qualified to write it. Keep it short—one paragraph max.
Step 2: Wait for us to get back to you. Usually takes like 5–7 business days. If we like your idea, we’ll say yes. If it’s not quite right, we’ll be honest.
Step 3: Write the full article. Follow what I mentioned above. Be genuine, truthful, and genuinely useful.
Step 4: Send it as a Google Doc or Word file. Include your SEO title, meta description, author bio, and notes about where internal links should go.
Step 5: We review it. Might be small edits, might be bigger changes. We’ll let you know what’s happening and when it goes live. Then you can share it everywhere.
That’s it. Pretty straightforward.
Why we actually need you
Here’s the honest part. Techies Times exists because people like you share what they actually know. Every article helps someone. It might assist users in finding an app that truly addresses their problem. It could help a developer learn how to create better products. Or it might prevent someone from wasting time on an overly hyped app.
Apps information is everywhere, but a lot of it is either outdated, overhyped, or just trying to get installs. We’re trying to be different. Honest. Actually helpful. Actually practical.
If you care about helping people build or find better apps, and you want an audience of people who will actually listen and take action, this is the place. I genuinely think what you know could change how someone approaches apps—whether they’re building them or choosing which ones to use.
Ready to write for us about apps? Send your pitch over. We’re actually excited to see what you’ve got.