Email: support@fhdevelopmentstudio.com
Include the product name, a short description of the issue or request, and any relevant screenshots, browser details, device details, or timing information so we can respond more efficiently and reduce back-and-forth.
FH Development Studio uses this inbox for both customer support and new project inquiries, so it is the right starting point whether you need help with a shipped product or want to discuss a new build, a higher-converting website, or a stronger next version of an existing experience.
What can this page be used for?
Product support questions, bug reports, feature feedback, privacy questions, website issues, and new business inquiries related to mobile or web development work.
How quickly will you respond?
Typical response time is 1 to 2 business days. More complex product questions or project inquiries may require additional follow-up after the first response, especially when technical review or scope clarification is needed.
What helps support move faster?
Include the app or project name, the behavior you expected, what happened instead, the device, browser, or platform involved, and when the issue occurred.
Can this page be used for development inquiries?
Yes. If you are reaching out about a new app, website, redesign, or internal tool, include a short summary of the problem you are trying to solve, the platforms involved, and any timing or launch expectations you already know.
Start with a focused, useful inquiry.
Clear context helps support requests move faster and helps project conversations start with stronger recommendations, tighter scope, and fewer expensive assumptions.
This inquiry form sends directly into the FH Development Studio admin workspace so project inquiries, product questions, and sales conversations can be reviewed, routed, and answered without unnecessary delay.
This request and bug form sends into the internal admin queue so the team can review bug reports, support issues, and feature requests for FHWebCheck, FHCams, websites, and client products in one place.
What to send for faster support and stronger recommendations.
Better context leads to faster troubleshooting, stronger recommendations, and clearer next steps with less back-and-forth.
For Product Support
If you are reaching out about an app issue, include the app name, device model, operating system version, what you expected to happen, and the specific behavior you saw instead.
- Helpful details include screenshots, timestamps, steps to reproduce the issue, and whether the problem happens consistently.
- If the issue involves notifications or network checks, note whether settings, Focus modes, or connectivity may be affecting behavior.
For New Project Inquiries
If you are contacting FH Development Studio about mobile or web development work, a short summary of your goals is the best place to start.
- Share what you want to build, who it is for, and whether it is a new build, redesign, or improvement to an existing product.
- Include timing, target platforms, and any launch constraints if those are already known so the early recommendation can be more useful.
Types of Requests We Can Help With
FH Development Studio can assist with product planning, interface refinement, marketing sites, iPhone app experiences, internal tools, and practical improvements to existing software that already needs a clearer path forward.
- FHWebCheck: monitoring questions, setup clarification, status interpretation, and usability feedback.
- FHCams: camera management questions, property organization, interface feedback, feature requests, and live-view troubleshooting.
- Custom software and websites: project scoping, redesign recommendations, conversion issues, performance problems, and support planning.
Suggested Inquiry Format
- Support: app or site name, device or browser, issue summary, expected behavior, and screenshots if available.
- New work: what you need built, who it is for, target platforms, timing, and whether this is a new product or an update to an existing one.
- Privacy questions: identify the product involved and the specific concern so we can respond clearly and directly.
What Happens Next
Most inquiries start with a direct response, a short clarification if needed, and a practical next step. For project work, that usually means clarifying scope, priorities, and platform needs before a recommendation is made on what to build first.
Quick answers for the current app.
FHWebCheck is built to keep website monitoring readable and actionable, with a clean overview screen, direct follow-up actions, organized settings, and detailed status context when users need to investigate further.
What does FHWebCheck help users see?
FHWebCheck gives users a monitoring view that highlights the sites they care about, the latest check timing, and whether each site is currently responding normally or needs attention.
What actions are available from the list?
From the site menu, users can open details, run a fresh check, review site history, edit the entry, copy the URL, open the site in Safari, or remove a site that no longer needs monitoring.
What can be controlled in settings?
The settings screen is designed to keep monitoring organized, including grouping options and monitoring behavior notes that explain how background refresh works on iPhone in real-world conditions.
What appears in website details?
The detail screen shows the current status, last check time, freshness, monitoring mode, notification preference, and the exact message returned by the latest result so users can understand the status before deciding what to do next.
Why is a site showing offline?
Temporary hosting issues, DNS problems, SSL errors, or short outages can all affect availability checks. If the issue appears briefly, try checking again after a short delay to confirm whether it was temporary.
How often are checks performed?
FHWebCheck performs checks when the app is opened and may run background activity according to iOS behavior. Background timing is not fully controlled by the app itself, so checks may not run on a fixed schedule in every situation.
Not receiving notifications?
Verify notification permissions in iPhone Settings and make sure Focus modes, summaries, or other notification controls are not delaying or suppressing alerts.
What should be included in a support message?
The most helpful messages include the monitored URL, what status you saw, when it happened, whether the issue was temporary or repeatable, and any screenshots that help explain the problem clearly.
Support for a cleaner camera experience across mixed hardware.
FHCams is designed to make older and newer camera systems feel more polished, more commercial, and easier to scan in real time, even when properties and device types vary.
What makes FHCams different?
FHCams is built to work with a wide range of camera makes, models, and ages while presenting them through a more unified, modern interface. The goal is to help users move from fragmented feeds and dated viewing tools to one cleaner experience that feels current, practical, and easier to trust.
What can users manage?
Users can organize cameras by property, review multiple locations from one overview, adjust refresh behavior, and keep camera lists readable as installations grow.
What should be included in an FHCams support request?
Include the property name, camera name, camera brand if known, the device you were using, and whether the issue involved loading, refresh timing, live view behavior, or interface presentation. Screenshots and timing details are especially helpful when the issue is intermittent.
Support for a network map that keeps device visibility practical.
FHNetworkMap is designed to help users see the structure of their local network, search devices faster, tune alerts, and keep the map understandable as equipment changes.
What does FHNetworkMap help users do?
FHNetworkMap gives users a visual network map, a searchable device list, practical alert settings, and an editing surface for organizing names, groups, and device details. The goal is to make local network visibility feel clearer and more useful without requiring enterprise-style tooling.
Why is a device missing or showing offline?
Devices may appear offline or may not show up if they are asleep, disconnected from the current network, filtered by the current view, blocked from discovery, or were not reachable during a recent scan. If the result looks temporary, run another scan and compare the seen timing before assuming the device is truly unavailable.
What can be adjusted in settings?
Users can tune auto-scan behavior, timeout values, notification preferences, offline thresholds, and default port-scan settings. Export tools are also available so the current map can be shared or reviewed outside the app when needed.
What can be edited for each device?
FHNetworkMap supports renaming devices, assigning groups, changing icons, configuring alert behavior, and enabling actions like Wake-on-LAN where the target device supports it. This helps the network map stay accurate as equipment moves, changes, or gets repurposed.
What should be included in a support message?
The most helpful support requests include the device name, local IP address if relevant, what screen you were using, what behavior looked wrong, whether the issue is repeatable, and screenshots or exported data if you are comfortable sharing them.