Project Overview
TAWSILA APP is imported from Behance as a Figma design case study. The project is categorized under Figma designs so it can be browsed separately from websites and mobile/backend implementation work.
TAWSILA APP is a Figma UI/UX design case study imported from Behance, published October 13, 2024, with focus areas including Figma, UI Design, UX Design, Driver app.
Open project
TAWSILA APP is imported from Behance as a Figma design case study. The project is categorized under Figma designs so it can be browsed separately from websites and mobile/backend implementation work.
The scraped project tags and tools identify the work around Figma, UI Design, UX Design, Driver app, car transport service, Vehicle Transportation, carservice, ui design. These tags are preserved as capabilities on the detail page so visitors can quickly understand the product type, UI direction, and design craft involved.
10 Behance-hosted project images were downloaded into the local portfolio asset folder and attached to this case study. The detail page uses those local files for the hero preview and gallery instead of hotlinking remote Behance images.
Source: Behance. Published: October 13, 2024. Last updated: October 13, 2024. Profile stats at scrape time: 80 Behance views and 4 appreciations. Original project URL: https://www.behance.net/gallery/210085207/TAWSILA-APP.
The technical footprint stays visible without turning the case study into a sparse list.
TAWSILA APP is imported from Behance as a Figma design case study. The project is categorized under Figma designs so it can be browsed separately from websites and mobile/backend implementation work.
The scraped project tags and tools identify the work around Figma, UI Design, UX Design, Driver app, car transport service, Vehicle Transportation, carservice, ui design. These tags are preserved as capabilities on the detail page so visitors can quickly understand the product type, UI direction, and design craft involved.
10 Behance-hosted project images were downloaded into the local portfolio asset folder and attached to this case study. The detail page uses those local files for the hero preview and gallery instead of hotlinking remote Behance images.


