Details
-
Type:
Rice Enhancement
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: Unspecified Future Release
-
Component/s: KRAD
-
Labels:None
-
Rice Theme:Kuali Application Business Drivers
-
Priority Score:5
-
Priority - KFS:Medium
-
Priority - KC:Low
-
Priority - KS:Low
-
Priority - Rice:Low
-
Theme:Platform Support
-
Application Impact:Low
-
Effort Estimate:High ~ 1000 hrs
Description
Develop capability to run Kuali Applications on mobile computing devices. Possibly extend KRAD and UI development frameworks to support Mobile operating systems.
Goals:
1. Allow for mobilization of Rice Services and KRAD User Interfaces
2. Work done for building standard screen user interfaces can be reused for mobile views. The mobilization is taken care as much as possible by the framework.
3. Allow for application developers to choose fields and groups that should not be present in the mobile view. Likewise, those fields and groups that should only be present for a mobile view.
4. Determination of which view to serve (standard screen or mobile) is handled by the framework.
5. The framework will take care of providing degradation of features that are not supported in a mobile environment.
6. Rendering of the mobile view will be done using the KME tag library.
Issue Links
- Trackbacks
-
![[Confluence: Kuali Rice]](/images/icons/generic_link_16.png "[Confluence: Kuali Rice]")
KRAD Integration with KME
This is a working document and comments are welcome. Intent The intent of this page is to document a proposal for the integration of the Rice KRAD module and the KME (Kuali Mobility Enterprise) project....
-
Kuali Rice Roadmap 2011
Timelines The team is currently developing Rice 2.0 and is scoping Rice 2.1, which will be released approximately 6 months after the 2.0 Full Release. View a more detailed timeline and breakdown of Rice 2.0 features at KULRICE:Rice 2....
-
Kuali Rice Roadmap 2012
Draft Timelines The team is currently developing Rice 2.0 and is scoping Rice 2.2, which will be released approximately 6 months after the 2.0 Full Release. View a more detailed timeline and breakdown of Rice 2.0 features at KULRICE:Rice 2....
-
Rice 2.3 Design and Analysis
Milestones and Timelines Teams Structure Team KRAD Jerry (DM) Brian Samuel Red Team Claus (DM) Steve Jeff Corey Blue Team Peter (DM) Martin Sona Shannon QA Team Erik Mayank Viral Shared...
-
Rice 2.3 Project Plan
DRAFT roadmap not finalized yet Overview Timeline: Proposed 9 month release (\ 1/15/139/15/13) Split: 68% new features/32% maintenance Roadmap Items # KRRM144 https://jira.kuali....
Activity
Setting Effort Estimate as Epic for now because depending on the scope of this, there could be a lot of work involved here.
I am interested in sponsoring this action, first I think we need a proposal for how we would approach this, one that could be clarified and estimated. My basic assumptions are mostly around mobile action list and doc search, and each of those complimented by a mobile=true request param, that the kns could use to render the mobile version of the doc based on the data dictionary and a new mobile view section of the doc data dictionary files.
Notes related to the potential work here https://wiki.kuali.org/display/KULRICE/KRAD+Integration+with+KME
Removing assignees that are no longer members of ARC. Current members of ARC will be asked to review and claim unassigned Roadmap items prior to our next voting cycle.
KS Comments - Support the idea that some actions or small tactical items should be supported on a mobile device, but it may not be feasible to have the whole UI development platform do this. Modifying KNS may not be the best approach.