As stupid as it sounds, you build small blocks and put them together.

In your case, build a console app, that (for example) creates basic sheets. Then you build a small text only interface to plug actual values into the file, then you can think about a GUI.

Many beginners (myself included) want to go from 1 to 100 immediately, but that's almost impossible. You tackle small problems first and then step by step go further.

You may have heard of startups building MVPs, minimum viable products. The basic core of what functionality you want to have. That's where you start.

This has always been my issue with programming. I can visualize how to build a chair, I know what I need to build it and I know what it needs to do. I know how screws work, and I understand when glue is applied.

But with programming it's like i know what the word wood is and I know what the word fabric is, but I haven't the slightest idea how I use any of it to make anything useful. I can't even start to build a plan because I don't even know what's needed for any specific thing.

At least you have an example of what you want to make, I don't even know what I want to make so it makes "figure it out" even harder lol

That is a really good point, and there isn't a one answer first all. If you're looking for a mobile app, then you could do Android studio or Swift for IOS. If you only want to develop one app for both, then maybe you should just do an electron app that is essentially just a website.

These tools will either have a visual interface editor, markdown language (like html), or a way to define visual components in code. After programming an app you can build, which will give you the appropriate executables for the different platforms.

If you're looking to start simple, then use something like pygame to learn the basics of using a visual interface.

What OS do you run? Are you planning on sharing this app with others? Should it be a web app?

Happy to help!

Look for some UI libraries. They provide functions and classes that you can call that will draw things to the screen. As for the executable part that varies per Language. If you want help dm me and maybe we can do a discord call!

this is where branches of coding splitoff, as learning the fundamentals of coding doesn't stop there, its a field where you have to pick up new skills on the go because not everyone needs it.

some people never touch apps because they might work backend or engineering, some people might not touh databases because they arent the ones dealing with CSV files. some people never touch web development (because its not engineering in some jurisdictions /s)

If i have to make a crude comparison, think of it like driving. basic driving knowlege is knowing how to drive a car. Knowing how to drive a car doesnt imply they know how to drive a boat, formula vehicle, big truck, forklift and such, so you need to go into further training for those, but you never should expect someone to cover all usecases.

Libraries. If you had to write everything from scratch, nothing would ever get done. You pick a UI library/framework that meets your needs and is supported in the language you're using, and go from there.

You can use a Web interface, it's absolutely hideous but it gets the job done. I hear QT is pretty easy to develop for and it's cross-platform.

There's pretty much only two ways you can go about it in my experience:

1. Fail forwards and try cobbling something together, constantly using search engines to fix errors or finding libraries or getting help with those libraries. One thing you'd have to figure out is an order of operations - what do you code and in what order, which might be tough for someone new but I'd say it's well worth it.

2. Find some tutorial to a project and try following it (those that have step by step guide on what you should do without letting you copy paste code), then using the knowledge you gain to do the way #1 above to hopefully have an easier time figuring out the order of operations, plan out your program and what you're gonna be coding.

Don't think you can avoid getting hands-on and coding something up by yourself. General coding tutorials can only get you so far and are often harmful if abused too much (aka being stuck in tutorial hell).

1. Turning into an executable is compiling as far as C goes. For Python, there probably is something somewhere to wrap a script into a .exe.

2. For the UI: what matters is the data you generate, not the fluff around it. As the other commenter said, start with a CLI program. You can easily nest several levels of menus if that's your thing. This allows you to have user input. Then for outputs you can do it to a .txt or .md file. Use simple text-based formats. Then once you've got that down you could build a GUI? But tbh I have never built a GUI and I've been programming for 10 years at this point so I can't help you out. There are simple cross-platform libraries you can use out there

What platforms would you like your app to run on? Then, which UI framework supporting those platforms would you like to use? Then, look at the framework's documentation to find a sample starter project that you can run as an app, and modify it from there

Actually this is the biggest hurdle in leaning how to code. You can blame the huge numbers of "learn to code in 24 hours" articles and videos online and the the influx of "5 day bootcamp" courses. Its like teaching someone the basics of how to drive a car but never teaching them the road rules and never taking them on the road.

A better analogy might be learning a foreign language. It's like teaching someone all the words in Spanish, but never putting them together in a conversation.

I'd argue that if you say "I know how to code, I know what variables are and how to print text to the console, how do I make an app?" Then actually you don't know how to code. You might know the basics of a programming language, and that is the first step in learning coding, but there are many steps after that.

I identified this gap a few years ago after seeing a couple of my friends (one finished a boot camp, and one finished a software development major at Uni) both were in this same situation. I determined there is a big gap between "knowing a programming language" and "knowing how to make software". It's like going from "I know how to write words" to "I know how to write a novel". It's not something that comes easy. It's something that can take time (often years) to get good at. This is the reason you see requirements like "3 years software development experience" on entry level programmer jobs. The number of people in your situation is incredibly high. The coding bootcamps churn them out by the hundreds every month.

A couple of years ago when I was between jobs, I created a Gumtree ad advertising "post-bootcamp" courses, that aimed at bridging this gap. It was a series of private 1on1 lessons aimed at teaching someone to go from "knowing how to code" to being "software developer" job ready. Lots of people have many different learning styles and different paths they took to this point. The key is focussing not on the giving them the missing information, but teaching the person how to identify what steps are missing and how to find resources to learn them (because that's the real missing knowledge wink).

Unfortunately I found some people didn't want to learn how to learn for themselves, and just wanted me to hand them the "secret missing parts" on a platter.

Harvards cs50 I believe has"the missing lecture" that talks about deployments and other activities surrounding programming.

If you want to learn how to make web apps you want to make sure the course includes deployments. Or get a specific course on the cloud platform you want to learn.

If this is not a meme...

You know how you have to look up... errors when you don't know what they mean?

That.

Figuring out how to do something specific, like UI, works just like that. All the time. It's "looking up how it works", then "messing around with it until it does" all the way down.

If you are just starting out, coding something in HTML and javascript might be intuitive, because you can see and run it right away. Otherwise you will have to figure out how to use some kind of UI framework in the language you're using. Because they're all different. Yeeeaaah...

I think it's harder for compiled languages and easier for interpreted ones.