DEV Community: WaseverinLabs

Why a Pricing Page Can Come Before Payment Integration

WaseverinLabs — Tue, 28 Jul 2026 08:15:46 +0000

A recent update to WASEVERIN Image Converter introduced a public Pricing page.

The image converter remains free, and payments are not enabled yet. The page currently explains what users can access today and previews a possible Pro plan for future features.

This raises a useful product question:

Should a SaaS product publish pricing before its payment system is ready?

The answer can be yes, as long as the difference between current and planned functionality is clear.

Pricing and payment are different features

A Pricing page communicates the product structure:

What is available for free
What may be included in a paid plan
How much that plan may cost
Whether the plan can currently be purchased

A payment system has a different responsibility. It handles checkout, payment confirmation, subscription status and access to paid features.

Separating these two areas allows a product to define its plans before introducing payment complexity.

Be clear about what is available

The most important requirement is transparency.

For WASEVERIN Image Converter, the current Free plan includes:

Browser-based image conversion
No image uploads
No account requirement
No watermark

The planned Pro option is displayed at $4.99 USD per month or $39 USD per year, but it is clearly marked as unavailable for purchase.

This avoids creating a checkout experience for features that are not ready.

Users should be able to understand the difference between available now and planned for later without reading additional documentation.

Keep the free workflow independent

The core conversion workflow remains unchanged:

Choose an image
Select an output format
Convert it locally
Download the result

This workflow should not depend on a payment provider or subscription service.

If payment support is added later, temporary billing failures should not prevent users from accessing the existing free converter.

Keeping the free workflow independent also makes future payment development easier to test and release separately.

Prepare without pretending

A Pricing page can prepare a product for future monetization without pretending that payment functionality already exists.

It provides an opportunity to validate:

Whether the Free and Pro distinction is understandable
Whether the planned price feels reasonable
Which features users expect from a paid plan
Whether users show interest before payment development begins

This feedback can be more useful than building a complete billing system based only on assumptions.

Final result

Publishing pricing before payments can work when the page is honest and the existing product remains unaffected.

The current update defines the Free plan, previews the planned Pro direction and keeps image conversion available without payment or registration.

Explore the Pricing page:

https://image.waseverin.com/pricing/

Would you publish pricing before integrating payments, or launch both at the same time?

Adding Optional Google Sign-In to a Browser-Based Image Converter

WaseverinLabs — Mon, 27 Jul 2026 11:17:16 +0000

A recent version update to WASEVERIN Image Converter introduced optional Google sign-in.

The converter was originally designed as a simple browser utility: choose an image, select an output format, convert it locally, and download the result.

Adding authentication created an important question:

How can a browser tool support user accounts without turning login into a requirement?

The answer was to treat sign-in as a separate capability rather than part of the conversion workflow.

Preserve the anonymous workflow

The first requirement was that the existing tool should continue working without an account.

Anonymous users can still:

Select an image.
Choose an output format.
Convert it in the browser.
Download the result.

The converter does not wait for account information before enabling these actions. If the login service is unavailable, image conversion should still work.

This separation prevents an optional feature from becoming an accidental dependency.

Keep identity separate from image processing

Authentication and image conversion handle different types of data.

Google sign-in deals with basic account identity. Image conversion deals with a file selected from the user's device.

The two flows should remain independent:

Optional sign-in -> account state

Image selection -> browser conversion -> local download

Signing in does not send the selected image through the authentication flow. It also does not create image storage or conversion history.

This keeps the original privacy model clear: account information is used only when a user chooses to sign in, while images continue to be processed locally.

OAuth configuration is part of the integration

Adding a Google button is only the visible part of OAuth.

The integration also requires:

A correctly configured Google Cloud project.
An authorized production domain.
An exact callback address.
Separate development and production settings.
Sensitive credentials that remain outside public frontend code.

OAuth configuration is strict. A difference in protocol, domain, path, or trailing slash can cause login to fail even when the interface is correct.

This is why authentication needs to be tested on the real production domain as well as during development.

Design more than two login states

A complete account experience needs more than "signed in" and "signed out."

The interface should also handle:

Checking the current account state.
Returning successfully from Google.
Cancelling authorization.
Displaying the user's name and profile image.
Confirming before signing out.
Showing a useful message when sign-out fails.
Restoring the account state after a page refresh.

These states are small individually, but together they determine whether authentication feels reliable.

The account control should also remain visually secondary. On a utility page, the main task is still image conversion.

Update privacy and product copy

Adding authentication changes how privacy claims should be written.

It is still accurate to say:

Images are processed locally.
An account is not required for conversion.
Images are not uploaded as part of the conversion workflow.

At the same time, the product should explain that basic account information is processed when a user chooses Google sign-in.

The privacy page, terms, navigation text, and FAQ should all describe the same behavior. Clear wording helps users understand the difference between optional account data and local image data.

Keep authentication out of the searchable surface

Public product pages can remain available to search engines, while authentication flows should stay outside the searchable surface. This keeps crawl reports cleaner and prevents search engines from entering external authorization flows.

SEO review may not seem related to Google sign-in, but it is part of completing the integration properly.

Test the upgrade without forgetting the original product

Authentication testing should include successful login, cancellation, refresh, logout, and failure states.

However, the most important regression test is still the original anonymous workflow:

Open the converter
-> choose an image
-> convert it
-> download the result

That flow should work before login, after logout, and even when authentication is temporarily unavailable.

Mobile navigation also needs attention because account names and profile images can take more space than a simple sign-in button.

Keep the upgrade focused

Adding Google sign-in does not mean the product must immediately add:

Mandatory registration.
A user dashboard.
Cloud image storage.
Conversion history.
A subscription requirement.

Authentication can remain a small, independent capability until another account feature has a clear purpose.

Final result

The version update adds Google account support without changing the core image conversion experience.

Users who want to sign in can do so. Users who only need a quick image conversion can continue without an account.

That balance keeps the tool simple while creating room for future account-related improvements.

Try the updated converter:

https://image.waseverin.com/

When you add authentication to a browser utility, do you keep it optional or make it part of the main workflow?

Building a Privacy-Friendly Image Converter in the Browser

WaseverinLabs — Fri, 24 Jul 2026 15:43:52 +0000

Many online image converters require users to upload their files to a remote server before processing.

For ordinary images this may be acceptable, but for personal photos, screenshots and documents, privacy becomes an important concern.

I built a lightweight online image converter that processes images directly in the browser.

It currently supports:

JPG
PNG
WebP
HEIC
GIF
SVG
BMP
TIFF

Why browser-based processing?

The main goal was to make image conversion simple, fast and privacy-friendly.

Because the conversion happens locally:

Images are not uploaded to a server
Users do not need to create an account
There is no installation process
Network upload time is avoided
Private files remain on the user’s device

The basic workflow is simple:

Select an image
Choose an output format
Convert the file
Download the result

Challenges

Browser-based image conversion still has some limitations.

Different browsers support image formats differently, especially formats such as HEIC and TIFF. Large images may also consume more device memory during processing.

Some format features may not be preserved after conversion. For example, transparency may be lost when converting to JPG, and animated images may become static depending on the selected output format.

These limitations need to be handled through clear prompts and error messages.

Convert Images Privately in Your Browser with WASEVERIN

WaseverinLabs — Thu, 23 Jul 2026 06:31:59 +0000

I built WASEVERIN Image Converter to make image conversion simpler, faster, and more private.

The goal is straightforward: users can choose an image, convert it to another format, and download the result without uploading the file to a remote server.

Try it here:

https://image.waseverin.com/

The Core Idea

Most online image converters rely on server-side processing.

That usually means users need to upload their files before conversion can begin.

WASEVERIN Image Converter uses a different approach. Supported image conversions run directly inside the browser on the user's device.

The basic workflow is simple:

Choose an image
Select a target format
Convert it locally
Download the result

Privacy-Friendly by Design

The converter is designed around local browser processing.

Images are not uploaded
Files are not stored
No account is required
No software installation is required
No watermark is added

This makes the tool useful for photos, screenshots, document images, design assets, and other files that users may prefer to keep on their own devices.

Supported Image Formats

The current version supports these input formats:

JPG
PNG
WebP
HEIC
GIF
SVG
BMP
TIFF

JPG and PNG are currently available as output formats.

Common conversion tasks include:

JPG to PNG
PNG to JPG
WebP to JPG
WebP to PNG
HEIC to JPG
HEIC to PNG
GIF to JPG
GIF to PNG
SVG to JPG
SVG to PNG
BMP to JPG
BMP to PNG
TIFF to JPG
TIFF to PNG

Animated GIF files are converted from the first frame. Animated output is not preserved.

A Simple Conversion Workflow

The interface is intentionally focused on the main task.

Users do not need to create an account or configure complicated options.

The workflow is:

Select an image from the device.
Choose the output format.
Start the local conversion.
Download the converted image.

The current limit is 10 MB or 40 megapixels per image.

Why Browser-Based Processing Matters

Processing images locally has several benefits:

Files do not need to travel to a server
Conversion can start directly on the device
The workflow is easy to understand
Users maintain control of their files
No desktop software is required

For everyday image conversion, browser-based processing provides a fast and practical alternative to server-based tools.

Built for Common Conversion Needs

WASEVERIN Image Converter can be used for:

Converting iPhone HEIC photos
Preparing JPG or PNG files for websites
Converting WebP images to JPG or PNG
Converting images for design tools
Converting SVG, BMP, or TIFF files
Quickly converting screenshots and other image assets

Try WASEVERIN Image Converter

Convert your first image online:

https://image.waseverin.com/

WASEVERIN Image Converter runs directly in supported modern desktop and mobile browsers.