Overview - Building the Citizen Reports application
The Citizen Reports application is part of the government demo portal site. It allows a resident to record and report issues that need repair. The idea is that a resident is more effective than government employees at identifying things that need attention such as potholes, broken fences, or graffiti covered walls.
The Citizen Reports application is the kind of application that work similarly and sometimes differently through multiple channels:
- Browse existing issues to determine if the government is already aware of it from a mobile device or a desktop computer.
- Report the issue to the government website using a mobile device or a desktop computer.
- Capture physical location and photograph of the item or place that needs repair using a mobile device.
- Browse status of repair action on a desktop computer.
The Citizen Reports application is functionally very similar to the Check In application which is also on the government demo portal. Both applications demonstrate how a portal application can be modified for use in a mobile device browser and a hybrid mobile application that can take pictures with the camera.
Since the implementation of this application is very similar to the Check In application described earlier in this wiki, we only give an overview in this article. To see the implementation detail of the Check In use case, refer to:
The Citizen Reports application uses profiling to change its behavior based on the access channel and the user's identity.
Accessed from a desktop browser, an anonymous user initially sees the following screen.
Accessed from a desktop browser, an authenticated government user initially sees the following screen.
Accessed from a mobile device, the user interface changes to enable users to create a new report. Here are the two interfaces (shown above) as seen on a mobile device.
Additional profiling with the **WPS Group Segment Handler** in a profileset is used to change the user interface based on JEE user roles.
Similarly to the Check In application, this application demonstrates how a WEF application that is designed for display on desktop can be tailored for the smaller display and unique feature set of a mobile device. This application uses two profileset handlers whereas the Check In application uses one. The same practice of applying profiles to builder inputs is used in both cases.
To see the implementation detail of the Check In use case, refer to: