I suppose you mean Real Time Apply ? That's very popular mode used when the shipping method of standby databases is synchronous (as you probably know Dataguard support two redolog shipping modes - asynchronous and synchronous). In your case of asynchronous redolog shipping there is one step further - use of Real Time Apply instead of shipping archived logs. So instead of waiting for redologs to become archived (either by database log switch or setting ARCHIVE_LAG_TARGET) and then shipped you could set Real Time Apply where blocks from the log buffer of the primary database are send directly to the standby logs of the standby database. The benefits are obvious - the lag is almost few seconds i.e. changes got applied on the standby few seconds after the primary, you don't have to worry whether the archivelogs are sent or not.
Here is link for more information about Real Time Apply at Oracle documentation Apply Services
In Real-Time Apply Data Guard applies the redo data without waiting the sequence to be completely received and archived.
The risk of using Real Time Apply is any user-based errors on the primary database will be instantly replicated to Standby Database.
The Flashback Database feature can help protect you from this risk.