e-commerce app guidelines required

[last cargo]

Hi,

To tell the truth, given some of the posts I’ve seen here I am a bit scared to share mine. But every journey starts with the first stumble. My background is a very specific are of bioinformatics and I have only vague idea what I am talking about here. However, I’ve been using rust for couple of years now (in my domain) and that is why I am here, and the fact that I decided to start a weekend project.

The project is to set up a small e-commerce site (locally hosted) for my bioinfo related digital products. The thing is these are quite “special” type of resources that are designed to be utilized only from inside a specific “app/framework”. The idea is that all these resources are preprocessed (that is segments are ) and stored on my server. You as a user can access them on demand if you pay (in imagery tokens preferably), and in order to prevent sharing the “secret souse” I have developed a decoder/runner/framework that can utilize client's request without disclosing the underlying “recipe”.

Therefore my question is, is Dioxus the right place to be given I am hoping to use it to write a simple e-commerce mobile app that should support the following:
1. user should be able to browse through a list of digital products
2. decide on its purchase and send a request to my server
3. on a server side the request should be processed by collecting elements required to build a product, encoding them specifically for the user and returning it back to a here/him once a transaction is finalized
4. user upon receiving the digital product can utilize it through its app whenever he/she wants

Any links , pointers to get me started, tutorials, example projects done in Dioxus are welcomed. I saw https://github.com/DioxusLabs/example-projects/tree/master/ecommerce-site as an example for the mobile app, are there any for the above use case suitable example for the back-end and how to connect it to the mobile app?

Thank you in advance !

Mxs

[next wave]

i mean, its surely feasable.

its just having a list of elements fetched from the server and implement payments & encryption (from what I understood)

tho the ecommerce-site example isn't up to date wtih the latest version of dioxus

you might want to look at axum for you back-end btw.
Or other frameworks such as actix or rocket if you prefer.
But imo axum is the best

for a starter point, i think that reading the doc is a very good start! If you understand everything in it, you shouldn't have any problems! (https://dioxuslabs.com/learn/0.5/)

[minor matrix]

have u done any frontend or backend work before?

[last cargo]

Thnx for the pointers 🙂

[last cargo]

well i did some, back in the day but that was perl cgi with mysql as part of backend . but i never done any mobile not payment processor, so far ... encryption is something i actively contributed in the past as well, from both scientific/theoretical and practical point 🙂 but let see. i have my first pointers so let me do the first step and see 🙃

[minor matrix]

are you making it specifically for mobile or desktop and web aswell?

[last cargo]

mobile primarily

[minor matrix]

you could do web and mobile both pretty easily im sure and just make a PWA to avoid the app store fees then it simplifies your payment processing to something like stripe and u get all platforms

but if you have any questions on backend and frontend and design stuff including auth and payment processing you can ask me, im new to dioxus so I won't be too much help with that though