I'm working on a unique project that involves building an online store for an embedded device, but there's a catch: it can't use JavaScript at all since the browser we're utilizing doesn't support it. While the backend can be built in any language, I need to ensure users can log in, browse products, and make purchases, all on a credit system where buying something costs one credit. Users shouldn't be able to buy the same item twice, and I'd like to ask for your insights on how best to design this.
Here's a rough outline of my setup: I'll have a database of products (with names, descriptions, unique IDs, and prices), users' info (including a secured email and password, plus a credits field), and a purchases table recording each transaction. The front end will require a user to log in to access anything, with a product listing page that links to individual product pages where users can either buy or see ownership status.
Once a product is selected for purchase, it should submit a form to the server to complete the transaction. If this approach sounds like I'm missing something or if you have suggestions for enhancements, I'd love to hear your thoughts!
5 Answers
You can definitely pull this off using plain HTML rendered server-side. Just keep in mind that the user experience might be quite basic without any JavaScript. You’ll be looking at full page reloads for any action, which could feel a bit slow or clunky.
If you’re going without JavaScript, you should be prepared to handle all user interactions via forms and a lot of page reloads. For instance, for a checkout process, the user will find entering and updating data slower, but it definitely doesn’t impact the core functionality. You'll want to ensure your backend handles things efficiently to minimize wait times on those reloads.
In your case, since it’s credit-based and lacks shipping complexities, keeping a lean interface should work out just great!
You don't actually *need* JavaScript for a store, but it does help with interactivity. Without it, every action will just reload the page, which can feel less responsive. Having a seriously streamlined backend to manage requests will help alleviate potential slowdowns you might face with multiple reloads.
That's true! Since it's on a minimal browser setup, keeping it user-friendly should be balanced against the lack of dynamic interactions.
It's perfectly feasible to build an online store without JavaScript! Your design will basically require full page reloads for each action, which is fine for a simple store. Honestly, I think JavaScript isn't critical for straightforward operations; it mostly enhances the user experience. If you're focused on functionality over flair, you can certainly get away with it!
I built a similar store back in '97, and it worked just fine, even without fancy scripts. Keeping it simple may just be what you need!
Since you’re dealing with a unique scenario, I’d recommend sticking with a language you’re most comfortable with for the backend. Maybe consider using minimal CSS for styling, and focus on server-rendered templates to speed things up. Keeping file sizes low will also be crucial given the device constraints, so aim for clean, simple layouts without much overhead.
Absolutely, and if you can avoid using larger images or unnecessary libraries, that would definitely help the performance!
What specific aspects of the experience do you think would suffer, though?