Search Results
A leach collection unit (LCU) was assembled to capture all leachate draining from a nursery container. An injection molded 2.8-L nursery container was plastic welded into the lid of a 7.6-L black plastic collection bucket so that the bottom 2.5 cm of the nursery container protruded through the lid. The LCU was designed to track total N release from CRFs without confounding effects of plant uptake or N immobilization. Total N released between any two sampling periods is determined by multiplying the N concentration in a leachate subsample × total leachate volume. The LCU were placed in a container nursery area with overhead irrigation. LCU were thoroughly leached before sampling the leach solution. To study the effects of substrate on N leach rates, Osmocote 18.0N–2.6P–9.9K (8 to 9 months 21 °C) was incorporated at 1.8 kg N/m3 using a locally available, bark-based substrate or medium-grade quartz sand. The experiment was conducted at Scotts Research locations in Apopka, Fla., and Marysville, Ohio. Osmocote incorporated into either a bark-based substrate or sand resulted in similar N release profiles. Although substrate did not affect N leach rate, quartz sand was recommended as the substrate in the leach collection system for polymer-coated CRFs. Quartz sand is chemically and biologically inert, does not immobilize nutrients and has low ion exchange capacity compared to bark-based potting substrates. More than 90% of the total nitrogen applied from Osmocote was recovered from leachate and unreleased N in fertilizer granules. This research has demonstrated the leach collection system as a reliable means to quantify nitrogen release rate of a polymer-coated CRF under nursery conditions. The LCU, when used with a crop plant, allows nutrient budget and nutrient uptake efficiency to be determined for CRFs.
With increased mobile device usage, mobile applications (apps) are emerging as an extension medium, well suited to “place-less” knowledge transfer. Conceptualizing, designing, and developing an app can be a daunting process. This article summarizes the considerations and steps that must be taken to successfully develop an app and is based on the authors’ experience developing two horticulture apps, IPMPro and IPMLite. These apps provide information for major pests and plant care tasks and prompt users to take action on time-sensitive tasks with push notifications scheduled specifically for their location. Topics such as selecting between a web app and a native app, choosing the platform(s) for native apps, and designing the user interface are covered. Whether to charge to download the app or have free access, and navigating the intra- and interinstitutional agreements and programming contract are also discussed. Lastly, the nonprogramming costs such as creating, editing, and uploading content, as well as ongoing app management and updates are discussed.
Mobile device applications (apps) have the potential to become a mainstream delivery method, providing services, information, and tools to extension clientele. Testing, promoting, and launching an app are key components supporting the successful development of this new technology. This article summarizes the considerations and steps that must be taken to successfully test, promote, and launch an app and is based on the authors’ experience developing two horticulture apps, IPMPro and IPMLite. These apps provide information for major pests and plant care tasks and prompt users to take action on time-sensitive tasks with push notifications scheduled specifically for their location. App testing and evaluation is a continual process. Effective tactics for app testing and evaluation include garnering focus group input throughout app development and postlaunch, in-house testing with simulators, beta testing and the advantages of services that enhance information gained during beta testing, and postlaunch evaluations. Differences in promotional and bulk purchasing options available among the two main device platforms, Android and iOS, are explored as are general preparations for marketing the launch of a new app. Finally, navigating the app submission process is discussed. Creating an app is an involved process, but one that can be rewarding and lead to a unique portal for extension clientele to access information, assistance, and tools.