Ideas needed: Fibery Mobile 🐌

[cannibalflea]

I echo many of the comments made here, in particular quick capture and offline mode. I think @Oshyan also covered a lot of the UI issues that generally exist on touch-based interfaces (not just limited to phones) which would hopefully be fixed even in the web-version running in mobile browsers.

My wishlist items are likely going to be in the “not going to happen” bucket but I thought I mention them anyway:

Dashboard/Custom Interfaces
I don’t know if this is an extension of quick capture, but I’ve always found adding new entities to fibery on a phone is super cumbersome because the UI is oriented towards mouse precision and larger screens. I recall that a few years ago there was some effort put towards creation of dashboards but it was abandoned. I think working on a mobile app and UI might be an opportunity to revive this effort to allow creators to build responsive interfaces (with regions, simple views, buttons, simple forms, …) that simplify working with fibery on mobile while also enabling dashboards and more complex views in the full web experience.

Form/View Customization

@tomp

Interactive conditional intelligent customisable forms

I think this is absolutely necessary no matter which version of fibery you work with. Multiple Views feature help with this to some extent, but I wish fibery’s UI was built from the ground up to support using the underlying entity data to control the UI elements. See following idea:

Setting field/UI properties based on conditions

With the excitement and discussions around [IN DEV] Entity-level permissions I have been thinking about field level permissions. I know that the Fibery team has said that field level permissions are not on the roadmap and unlikely in the near term (see below from recent posts as well as Field-level permissions request): There has also been some discussion that maybe view permissions and multi entity views might make this not as a big deal: However, I was thinking that there might be another …

Device Hardware Access
I think it would be super helpful to have access to some of the mobile device sensors/features which are currently inaccessible in fibery. These include:

• Camera: being able to capture and add photos to fibery entities from the app or read barcodes/qr codes
• NFC: being able to scan nfc tags to record something (e.g. checkout an object) or trigger an automation
• GPS: allowing fibery maps to show user’s current position on a map and also use this information to filter entities based on proximity would be fantastic. This might also be an opportunity to give map views some (see some ideas here)

I can imagine most of these device/hardware features would not be very important to conventional fibery users, but they would open-up fibery’s use to quite a few other use cases which are mobile-first (e.g. inventory management, asset management, field inspections, …). I know being web-based as opposed to a native app might mean some of this is not even possible, I still thought I should put the idea out there.