subz390

Kiosk App on Raspberry Pi

• I have a personal project that I'm developing into a Kiosk app and am considering deploying it on a RaspberryPi as a semi-portable controller user interface.
• I'm new to RaspberryPi, I know my way around Debian though, and so I've researched a few Electron tutorials on using Electron on a RaspberryPI and they seem to be what I'm looking for.
• However, I'd love to hear your comments and suggestions in working with Electron on the RaspberryPi, in particular in Kiosk with a touchscreen for user input.
• What's the performance like, are there memory constraints, any reliability issues I should be aware of?
• Once the project is at a working stage I plan to open source it on my GitHub for further input and development.
• I'm a long term JavaScript developer (since the late 90's for real I was there when JS was first released, unashamed Vanilla.JS fanboi)
• I write for the browser and server backend environments using Web technologies and Node.js.

I think with anything related to personal development is about comfort zone management. Being too comfortable one can feel bored, too outside ones comfort zone one may feel out of their depth. I'm sure there's more to this down the rabbit hole of psychology. However I found learning about motivation and striking the right balance of extending myself has truly helped keep me pushing forward at a steady pace. In the end do projects that are motivate you whilst incorporating learning as you go. So pick a project that you know is possible, that you can achieve if you put the work and effort in, and that the outcome of it will be as you expect. I think even the perfectionist in you will find that satisfying.

The way I'd approach this is to carry out a survey. Prioritise a list of important criteria, such as performance, functionality, and cost. For example with MongoDB you can archive documents if the data not immediately required to save on costs at the expense of instant access, but if that fits your use case model then you can use that feature. So create a use case test project that actually uses both services as per your use case and see for yourself the results of the tests. Along the way you'll encounter issues perculiar to each platform that you can factor into your final decision, such as comparing how easy it is to use their API, or that the documentation is sparce or confusing. From there you'll have an informed decision and you'll be confident investing further resources into it.

I don't think there's a decision to be made, aren't they different products and services? GitHub is traditionally an online repository based around Git versioning. GitHub have expanded into other things since Microsoft came in though. Nevertheless I recommend seriously taking the time to work through the very steep learning curve of setting up a local development environment. You could start by using Visual Studio Code and get a free GitHub account to push your private projects onto. If anything it'll be a free offsite backup of your work. You'll need to install Git to take care of your local repository as well as NPM and also look at Yarn. Have this on your priority list, do some research, gather links, tutorials, downloads etc and take a week out to get it done when you feel you're at the stage where you'd like to be more organised. You could start by trying VSCode see whether you like the features and using it as an editor. Look at other editors and so on.