Want to do a h5+app, similar to the address book on the mobile phone, in each contact can add pictures and other personal information, I would like to ask how to choose the technology.

problem description

I"m going to write it as an h5 project, and then package it into an Android or ios package on HBuilder. It doesn"t have much function, but it just saves contact information. Some pictures and txt files may be saved in each contact. If you are not going to make it online, then if you store this area, which kind of local storage is better? will these local storage be cleaned up if the mobile phone cleans up the garbage?

the environmental background of the problems and what methods you have tried

related codes

/ / Please paste the code text below (do not replace the code with pictures)

what result do you expect? What is the error message actually seen?

Nov.10,2021

Hbuilder is essentially webview
storage methods localstorage, websql, indexedDB and plus's own io can directly deal with local files.
either browser local storage may be cleaned up, although it is unlikely.
it is recommended that you still need to do a cloud feature.

For more details, please see
https://www.cnblogs.com/skyso.

on the following page.

Native js can consider using localForage . Chinese document is mentioned in Readme. The advantage is that you can automatically choose whether the bottom layer should use IndexedDB or WebSQL, or if you don't support it, then localStorage, you just use the API encapsulated by it.
however, from a product point of view, it is more recommended that you directly use Mini Program to implement it, and the goose factory will help you lay the groundwork. There should be less holes to step on than if you encapsulate APP and then adapt to both ends. If you don't want to rely too much on platforms, there are still some multi-end platforms made with Vue or React. What comes out can be adapted to platforms such as Mini Program, H5 and RN at the same time (for example, the concave and convex Taro , you can look for it again). I think it is more cost-effective than using Hbuilder (of course, just for discussion).

Menu