Frequently Asked Questions

PenDevs provides UI/UX and Figma design, Figma-to-Elementor production, authorized Elementor website recreation, custom WordPress sites, themes and plugins, web and mobile apps, QA testing, WordPress maintenance, migrations, video editing and white-label agency support.

Send the project goal, relevant links, required services, approximate budget and desired timing. PenDevs reviews the brief, asks focused questions and recommends a discovery step, estimate or technical audit.

A focused landing page may take weeks while a custom website, plugin or application can require multiple phases. Timing is confirmed only after scope, content readiness, integrations and review responsibilities are understood.

Ownership and licensing are stated in the project agreement. Custom deliverables normally transfer after required payments, while WordPress, Elementor, fonts, stock assets and third-party software remain subject to their original licenses.

Yes. Confidentiality, client-facing boundaries, communication channels and delivery responsibilities can be agreed before access or sensitive project details are shared.

No responsible agency can guarantee rankings or citations. PenDevs can implement crawlable structure, useful metadata, structured data, internal linking and accessible content, but search engines and AI systems decide what they index and surface.

Useful inputs include the business goal, audience, sitemap or required pages, brand assets, draft content, competitor context and examples of preferences. PenDevs can help organize an incomplete brief during discovery.

The agreed handoff can include the organized Figma source file, components, styles and exportable assets. Any third-party fonts, icons or stock assets remain subject to their license terms.

The implementation is compared at agreed desktop, tablet and mobile widths. Some adjustments may be recommended for fluid content, accessibility, performance or limitations in the design that are not visible in static screens.

Yes. Global styles and reusable components are used where practical, and the handoff can include a short walkthrough. Complex areas may be protected or documented to reduce accidental layout changes.

PenDevs only recreates websites when the client owns the source, has authorization or is commissioning an original implementation based on lawful references. Protected text, imagery, code and brand assets are not copied without permission.

Elementor is useful for flexible marketing pages and team editing. A custom theme can be better for a distinctive system, tighter performance control or structured templates. The right choice depends on editing needs, budget and long-term ownership.

Custom work makes sense when content types, integrations, editorial workflows or interface requirements cannot be served cleanly by an existing theme. It should solve a real operational need, not add complexity for its own sake.

The implementation uses appropriate capabilities, nonces, sanitization, escaping and WordPress APIs. Security depends on the complete hosting and plugin environment, so updates, access control and ongoing review still matter after launch.

Often, yes. Feasibility depends on the service API, authentication, rate limits, documentation and account permissions. Discovery confirms data flow, error handling and who owns each external dependency.

The decision considers audience, device features, offline needs, distribution, budget and release timing. A responsive web application or cross-platform build may validate the product before separate native applications are justified.

Release preparation can be included, but the client normally owns the Apple and Google developer accounts and accepts platform agreements. Approval timing and acceptance are controlled by the stores, not PenDevs.

Scope can include functional journeys, responsive layouts, browsers, forms, content, roles, integrations and regression checks. Performance, accessibility, security or automation require explicit scope and tools.

Each confirmed defect can include a concise title, environment, severity, reproduction steps, expected and actual results, and supporting screenshot or video evidence. Retesting is included only when stated in scope.

Maintenance is risk-based. Routine updates may be handled during a scheduled window, while higher-risk theme, plugin or major WordPress releases may be backed up and tested first. Exact practice depends on the selected plan and hosting setup.

Existing malware, blacklisting or serious technical debt is normally assessed as a separate recovery project. After remediation, an ongoing plan can help with monitoring, controlled updates and backups.

Many transfers can be prepared before DNS changes, reducing interruption. Actual downtime depends on hosting access, DNS control, site behavior and email configuration. The migration plan identifies these risks before cutover.

Not automatically. Website hosting and email may be separate services. Mailbox migration, DNS records and deliverability checks must be identified and scoped independently when they are part of the move.

Provide the highest-quality footage, audio, logo and brand assets available, along with the target format, duration, references and required text. Confirm that you have permission to use every supplied asset.