The APEX 4.2 wish list was certainly a success when it came to encouraging the community to speak out with what they wanted. There were many features suggested, all with varying degrees of complexity in regard to fitting in with the current data model & infrastructure. I have drafted a retrospective post to analyse some hits & misses.
Oracle now provides a dedicated application to listen your APEX feature requests. There is a similar one for SQL Developer.
|APEX Feature Request application|
What big change would you like to see in APEX 5?
Eight ideas to get your brain juices flowing:
- A major restructure of Interactive Reports, offering more control with UI options, sharing reports, migration
- Bigger, more dedicated leap into responsive web design for at least 3 devices, offering more features
- A super easy to integrate, supported, WYSIWYG reporting engine/development tool
- Remotely integrated migration engines operating over a database link
- Built-in version control, perhaps with super-changed build option features
- A simpler (than plug-ins) transparent porting facility to allow developers more easily integrate jQuery plug-ins, typically for menus & lists
- More cross-application features, particularly the management of subscriptions
- More integrated use of page aliasing, optionally applied "instead of" page numbers, and of course
You'll get more awareness for these ideas using the application than relying on post 42 on 18 pages of posts, but it would be nice to see your big ideas repeated as comments/forum posts regardless to help seed activity.
The APEX development team are are listening.