Oracle APEX Reviews

I would definitively use APEX for small (department size) applications that can be developed and maintained by a small development team, without a complex design/develop/test/deploy process.
Also, to generate all basic CRUD on complex applications, rather than programming them using other languages (Java. c#, etc) and having more complex deployment processes.

Oracle Application Express is good for easy and fast application and reports development. You can develop entire applications and you do not need another web server. However, you cannot access the source code of applications built in Oracle Application Express.

Very well suited for medium enterprise applications.

If you need rapid application development, this is the tool that you need. It is easy to use, and you can develop an application easily and fast. But they should really improve the version control, sometimes its hard to use.

Best for web applications. Less appropriate, however, for mobile applications. Applications that deal with businesses are quite useful.

It is appropriate for database application development supporting data driven processes, online transaction processing, BI/reports/analytics ... for addressing about any business data processing need I can think of. Oracle Application Express is fantastic for creating beautiful rich user interfaces with support for all major browsers rendering well on a range of devices. It is less appropriate for applications requiring native low level access to device peripherals and is less appropriate for applications that must execute offline without network/internet connection to supporting application and database servers.

Almost any business requirement with data-centric aspects can be covered - no limitations.
ERP, CRM, HCM, Financials, mobile apps.

Although I don't utilize it very much, graphs seem less important but Oracle JET should give what you need.

APEX is data-centric. When you have a data-driven company with large data flows, APEX is a great choice. Because APEX is installed directly in the database, the data is always available. The Universal Theme allows you to make responsive applications without the need to write extra code. So users can access the data even their phones/tablets when they're on location. Applications build with APEX are most of the times multi-page applications. Today single-page applications (SSA) are more popular. Building an SSA can be quite difficult with APEX.

It is very good when you have an application like Forms and need additional functionality (features) that you can't have in forms (dashboards, predefined IR with charts). It's a good use of external sources (web sources, REST API) and ata visualization. I haven't tried it yet, but I don't know how it functions in complex pages (a lot of client controls, few hundred fields). For example, we have physician reports or discharge summaries, and nurse documentation about the care of a patient.

It's well suited if you need to display (or enter/change) data from an Oracle database. If you (or your customer) think you definitely need a native app, then it is not a good fit. Creating a dashboard with different kinds of charts and KPI's is easy using APEX. If you need a real data-mining solution, then you better switch to Oracle Analytics. As APEX offers an easy interface for RESTful services, you can also create forms, reports, and charts upon any RESTful service that's available on the internet -- either within or outside your organization.

Oracle Application Express is great for small applications, where you have a few pages. You upload an excel file, create a interactive grid, create user authorization and everybody can work on this grid. You can develop an application in hours or a few days.

I think it's less appropriate when a customer has a lot of special front-end wishes. In this case, it would be better to start with Angular and generate the front-end all manually.

In our scenario, I think it is the best instrument for data correction and data validation.

Oracle Application Express can essentially be used for any web application that needs to talk to an Oracle Database. Simple applications to view/edit data can be turned out in next to no time with the built-in reports allowing fine-grained control for the end user. It really shines when used for tasks such as dashboard management or basic manipulation of data, all of which can be done with next to no code.

For less standardized tasks, the architecture will allow the use of other web technologies. I have, for instance, incorporated Google Maps into Oracle Application Express in order to visually show data, such as the operating areas, for our consultants. Setting this up in the Application Express framework is relatively straightforward allowing me to concentrate on the heavy lifting in PL/SQL.

The only major area I've found that it isn't well suited in currently is outputting anything printable, typically requiring the use of some 3rd party hardware or Oracle BI (if money is no object). I have also run into issues when working with larger teams as it doesn't lend itself well to source control with all the pages being stored in the database itself.

No matter where you live, you can build scalable, secure enterprise apps. If you want to work in the same workspace as your team, you will need an Internet connection.

Capturing data and uploading documents. Easy design for the template.

Oracle Application Express is well suited if you have a big dataset which has to be visualized in a graphic manner or if you have to provide a good solution to create, edit or manipulate data by end-users in a web-application. It is also well suited if you need to create KPIs that might already be in place and they just have to be brought to the surface in the browser!

If a company is has a need to extend an existing Oracle rep, cis, CRM or other large platform. Also if a company has Oracle-familiar resources and would like to build their own applications or modules to interact with another application.

It is a nice and inexpensive tool, ideal to extend the functionality of the systems, and offer users good reports, graphics and easy-to-use applications, developed with speed and low maintenance cost. We don’t use it when we have to customize standard processes in our ERP, mainly because we are SOX compliant, and it is more difficult to us to prove our auditors that we respect and accomplish with all the validations and controls they demand.

I feel like this system works well for most lines of business. It may not work well for organizations that only have a few people, but it is great when your organization is larger and/or spread out across multiple states. It allows for team members to have networking in that aspect.

We have converted a lot of old SharePoint processes to Apex applications. We are developing new applications using this tool. Most of the applications are being utilized to transition old processes to make them more efficient. The worst part of the software is having to strictly follow the structure, we cannot put as many columns and items as we would like and we would enjoy that customization.

If you need an application linked to an Oracle database, use APEX.

I would recommend it completely if you need the production of functional sites quickly. Simple approvals flow through different hierarchical levels can be simulated through groups and roles, but if the need is more complex flows for robust systems, I would advise opting for other programming frameworks.

Oracle APEX is a Versatile tool. Though it is database specific, it can be used with many other different technologies. Also, it is accessible from browser as well as mobile.

If you use Oracle Database and want to create an application that uses your data, this is a free development tool and it's amazing what it can do.