Scratch is a simple drag and drop app kids use to learn to code. I've seen kids create pretty elaborate games with it. Maybe you could play with that and figure out if your concept is in fact simple enough to create on your own.
this post was submitted on 24 Apr 2025
47 points (96.1% liked)
No Stupid Questions
40751 readers
454 users here now
No such thing. Ask away!
!nostupidquestions is a community dedicated to being helpful and answering each others' questions on various topics.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules (interactive)
Rule 1- All posts must be legitimate questions. All post titles must include a question.
All posts must be legitimate questions, and all post titles must include a question. Questions that are joke or trolling questions, memes, song lyrics as title, etc. are not allowed here. See Rule 6 for all exceptions.
Rule 2- Your question subject cannot be illegal or NSFW material.
Your question subject cannot be illegal or NSFW material. You will be warned first, banned second.
Rule 3- Do not seek mental, medical and professional help here.
Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.
Rule 4- No self promotion or upvote-farming of any kind.
That's it.
Rule 5- No baiting or sealioning or promoting an agenda.
Questions which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.
Rule 6- Regarding META posts and joke questions.
Provided it is about the community itself, you may post non-question posts using the [META] tag on your post title.
On fridays, you are allowed to post meme and troll questions, on the condition that it's in text format only, and conforms with our other rules. These posts MUST include the [NSQ Friday] tag in their title.
If you post a serious question on friday and are looking only for legitimate answers, then please include the [Serious] tag on your post. Irrelevant replies will then be removed by moderators.
Rule 7- You can't intentionally annoy, mock, or harass other members.
If you intentionally annoy, mock, harass, or discriminate against any individual member, you will be removed.
Likewise, if you are a member, sympathiser or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people, and you were provably vocal about your hate, then you will be banned on sight.
Rule 8- All comments should try to stay relevant to their parent content.
Rule 9- Reposts from other platforms are not allowed.
Let everyone have their own content.
Rule 10- Majority of bots aren't allowed to participate here. This includes using AI responses and summaries.
Credits
Our breathtaking icon was bestowed upon us by @Cevilia!
The greatest banner of all time: by @TheOneWithTheHair!
founded 2 years ago
MODERATORS
I would encourage you to try to learn gaem development, it’s fun :D I’ve personally tried Unity and Godot and prefer the latter bc it’s oepn-source and I like the workflow but both are good.
Brackeys makes the best Unity tutorials and he’s starting to make some pretty good Godot ones too. My first games were pretty much following along the Brackeys tutorials and then trying to extend the game by adding more levels, gimmicks, etc. and learning a bunch of new things along the way. Some more Godot specific tutorials I like are GDQuest and HeartBeast.
Good luck on your game development journey! :D
If you want to open source it you can already open source your documents.
You can publish them and see if others like the idea and join you.
Maybe create a lemmy community to organize people who want to join.
I would be concerned about giving away their idea and having someone steal it
But I'm cynical that way
If you make it open source then they can steal it, too.
Why not look at it in positive light? If somebody steals it, they help you popularize the game and they show you another way to implement it.
Of course, first mover advantage, there is some truth to your worries. Still, should you quit because you don't find a way to implement the game, consider giving it a last chance by opening up the process.
I meant if you give away the idea by open sourcing it, by the time you're ready with your project the idea exists in dozens of forms already and you now look like a knock off.
Then it's too late for you to have much success
First mover advantage, is this what you mean by first mover advantage?
This is course assumes you care about popularity/success of your product, if you only care about it existing and not performing on it then yes opening it up out of the gate makes a entirely too much sense.... Even for my cynical ass
is this what you mean by first mover advantage?
Yes.
When you say you're having an awful time; which part are you struggling with?
I'm learning Game Maker rn, would be willing to try to figure out how to implement some of the features as a co-learning thing, if you're interested in some random dipshit
The real question is how organized your design doc(s) is/are, honestly, you could probably make whatever you're thinking about in RPG maker if you weren't afraid of it being generic AF so long as the organization is solid
Freecodecamp.org
Three things based on other comments here:
(1) is free, try that!
Be wary with this. They may be free for students or small deployment situations, but may have increasingly agressive demands as your user base increases in size or your seek some kind of profitability. I wouldn't panic about, but do make sure to carefully review the licensing terms for ALL tools that you use in your process.
(2) Learning/Tutorials
Depends a bit on how you learn best. Youtube almost always has some good instructional videos. Most of the major tool/engine makers have large libraries of tutorials to draw from as well. Even very experienced programmers routinely have dozens of browser tabs that start from web searches that read "<name of my game engine/platform> how to do ".
(3) If you look to hire or contract out some of the work, just realize that you will very often only get what you really pay for. Quality work costs more. One option you have is to spend the next year or three doing everything you can yourself. Get as close to complete as you can. Then go to something like Kickstarter and look for completion funds. "Look at how complete the game is. If I can just get a little bit of money, I can hire a professional to do that one part that I couldn't do myself". This is especially usual for getting access to skills like art, music, voice acting, etc.
In my own experience, i would do #3, then take that and do# 2 after reviewing different #1s
If the code you pay for makes a game that does something close to what you wanted, you then have that to work with and go on.
(I don't know if this is how things work in the real world so please forgive if it's not quite right)
Use it like an alpha or pre alpha build, and as a reference for how the coding can be used to do different things but specifically for your project.
It may be a horror show to try and fix someone else's code, but for someone who doesn't know already, it would be very useful as a learning environment that was created uniquely for your project, and then you start asking/looking for very specific help
You could then post snippets and ask about anything that you struggling with, or even use AI to explain it(that may be terrible or it may not be, you can let me know lol)
(I'm not a programmer, but i took a class in highschool, 25 years ago and did a couple things with logowriter, and turbopascal)
Where do I go
You go to a bank, because you need money to pay your programmer.
You could try hiring someone on Fiverr. There are plenty of freelancers looking to take on work, and they should give you some level of customer service, and set your expectations for what actually needs to be done.
Thank you! I hope OP sees this
At this time, you are the only person to give an to answer OPs question. Seems everyone else can't read the question
When you hear “I’ve got this great app idea—it just needs someone to code it,” it may sound to you like you’re halfway there. But from a programmer’s point of view, that’s actually the least interesting and riskiest way to start. Here’s why:
1. There’s no roadmap—just “code this”
- Undefined scope: If all I have is a vague idea, I don’t know what “done” even looks like. Am I building a basic prototype? A polished product? What features must it have on day one, and what can wait until later?
- Endless scope creep: Without clear boundaries, every conversation becomes “Just one more little thing,” and suddenly what was supposed to be a weekend project balloons into months (or years).
2. You’re asking me to invent half the project
- UI/UX design: How should it look and feel? What screens go where? How do users navigate? That’s a specialized discipline all its own.
- Product strategy: Who exactly is this for? Why will they use it? How will you reach those users? If you can’t answer that, I can’t write code that solves a real problem.
- Testing & polish: Code needs testing, bug-fixing, documentation, deployment, maintenance… none of which you’ve accounted for.
3. No incentives, no commitment
- Why me? Great programmers want to work on problems they find meaningful, challenging, or fun—and ideally get compensated for their time. “Just code my idea” won’t light anyone’s fire.
- Who owns it? If I invest weekends or nights building your vision, what do I get? Equity? Pay? Recognition? Without a clear agreement, it’s a recipe for frustration and resentment.
- Long-term support: Apps need updates, server maintenance, user support. If you haven’t thought through who handles that, you’re building technical debt.
4. Real success stories are team sports
- Cross-functional collaboration: The best apps come from teams that include product thinkers, designers, data analysts, marketers—and yes, developers. You can’t outsource half the work and expect a hit.
- Iterate and learn: You start with sketches or clickable wireframes, show them to real people, iterate, then bring in developers to build a minimum viable product. That way, you’re coding something people actually want.
What you can do instead
- Write a one-page spec: Describe the core problem, your ideal user, key features, and success metrics.
- Mock it up: Even hand-drawn sketches of each screen help communicate your vision.
- Validate your idea: Talk to potential users. If they’re excited, you’ve got something to build.
- Find a partner: A developer who’s excited by your clear plan—and who sees a fair path to reward for their effort.
In short: coding is only about 20% of what it takes to launch a successful app. If you can’t show a programmer that you’ve thought through the other 80%, they’ll politely pass—because turning a half-baked idea into a working product is a lot more work (and risk) than it looks.
This response is sort of the issue I keep running into. I've already gotten this talk, learned from it, and moved forward. I now have nearly two notebooks detailing every mechanic, mock ups of ui design, animation ideas, sprites, complex dice roll mechanics to engage with tables for content generation, and even a roadmap for the first 15 major updates to assess timeline based on the time it takes to convert to a digital format. I'm not even looking to offload the work, database entries are like 90% of this.
I'm here asking because I don't know how to do the next part where I find the other 20% of making this happen.
I really like how they ended that comment with
Find a partner: A developer who’s excited by your clear plan—and who sees a fair path to reward for their effort.
As if that isnt what you are literally doing by posting here
Feels like an AI answer.
Upwork is a website where you can search and hire freelance software devs - and there are other, similar sites out there as well. Vetting the person you hire will be a whole process in itself.
If you believe data entry is 80% of the work here, you do not in the slightest understand the other ”20%”. I can assure you that data entry is the least of your problem. If you have the data, a script to enter it into a DB will be the least of the worries here.
That’s also why you likely can pick someone up on Fiverr to do it for you for a couple of hundred bucks. Or do it yourself. Want someone to build your app, even without the data entry? You’re looking at thousands.
And that’s basically what you will need to do. Pay someone to do the work you can’t. Look at upwork or similar sites.
I get paid $150/h to write code at work (horrible pay compared to many parts of the world). Why would I spend months on your project for less?
What do you think the response would be if you asked on a remodelling forum, how you were to complete your new kitchen? You’ve bought the tools needed, the material. Drawings are made. It’s just the last ”20%” left. Where can I find someone to do it? Well, it’s not the last 20%. The job hasn’t even started yet. And you pay someone, or learn to do it yourself.
The top level comment by user listless is the one that said coding is 20%
OP is just trying to explain that they aren't trying to hand this idea to someone and then do nothing.
You could be more kind and encouraging
This is No Stupid Questions
And OP is just asking for help and getting a lot of unnecessary heat here
OP is NOT in software industry, dont get offended if they say some things based on what other people have told them
We should be helping and encouraging, not tearing people down here
Peace be with you
I get paid $150/h to write code at work (horrible pay compared to many parts of the world).
What?
Some constructive criticism? This is info you should have put in OP, it would likely have made the thread more productive.
I got another suggestion, use the game development design to start. This will get all of the foundations of the games design that you just need to implement.
Edit: GDD(Game Design Document) search what it is and what’s the purpose and it will help the most.
I have even bigger aversions to anyone coming with "I have this fully specced Game Design Document"
Why? It’s literally proving that you did the 80%?
"Waterfall process" is a curseword in software development for a reason.
To me it proves the person is thinks that a game can be created without prototyping and iteration. In addition to only doing 10% of the work, they are under the illusion that they have done 80% and completing it is just a rote exercise. They have also overdesigned untested features and mechanics which makes any iteration harder. I'd have to break their thing down and iterate over the parts with them while also explaining this to them.
It's just double worst.
To be fair tho this is what happens when you get involved with passionate but ignorant people? Where else would people go to get help if you just shut them down? This seems like gatekeeping but maybe there needs to be more context to game development in general? This is about someone who has an idea but no knowledge about implementation.
It doesn't sound like gatekeeping to me.
Gatekeeping is trying to prevent someone from doing something. This sounds more like a lot of people just saying that it sounds like a nightmare for reasons non-devs might have trouble understanding and they wouldn't want to touch it.