Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(2 edits)

> Why use this method anyways.

My reasoning is what I'm building will either be used a ton (resulting in zillions of files), or not at all. I really can't see having any casual users. Given that, not having working file management seems a huge usability hit. It'd be crippling for me, anyway, to have a broken file manager, and not be able to use a CLI as most people can't.

Do people just...not work that way, anymore? I see so many apps that just hide all my files in their config directory and give me a half-implemented riff on Norton Commmander to manage them with like that's a normal thing to do. I thought it was because they were low-quailty ports of phone apps. Is that an accepted practice in 2023?

I still do not get it.

Do you expect people to have files created by your app reside in a user folder and users to navigate there with the os and open the files?

Or do you expect people to open the app and then use the app to open different files.

Because file extensions on system level only matter for scenario 1. Or is this fundamentally different on mac? When I open , for example, a picture viewer and select open file, it prefilters the folder I am looking at, with pictures. But for a picture viewer, it is handy to use the os file browser and just randomly open a file, without opening the app first.