Search Results

You are looking at 1 - 3 of 3 items for

  • Author or Editor: Karen Rane x
Clear All Modify Search

Ten muskmelon (Cucumis melo L.) cultivars were tested for their susceptibility to bacterial wilt, caused by Erwinia trucheiphila (Smith) Bergey, Harrison, Breed, Hammer and Huntoon and vectored by the striped cucumber beetle Acalymma vittatum (F). `Superstar', `Rising Star', `Pulsar', `Caravelle', `Cordele', `Legend', `Makdimon', `Galia', `Rocky Sweet', and `Passport' were used in field studies to determine the number of striped cucumber beetles, feeding damage, and incidence of bacterial wilt. `Makdimon' and `Rocky Sweet' hosted significantly more beetles than the other cultivars. These two cultivars and `Legend' and `Cordele' had much more feeding damage and a significantly higher incidence of bacterial wilt than the others. A greenhouse experiment was conducted with seven of the cultivars to test their susceptibility to bacterial wilt when directly inoculated with the causal agent. All cultivars were equally susceptible to the disease when it was introduced directly into the plant. Selective feeding by striped cucumber beetles was probably most responsible for `Makdimon', `Rocky Sweet', `Legend', and `Cordele' having greater incidences of bacterial wilt than the other cultivars.

Free access

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.

Full access

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.

Full access