Help Center

Frequently Asked Questions

The Process

How the Process Works

  1. First, the D-U-N-S number is obtained (free) and the Google Play developer account is set up (a one-time $25 USD fee, subject to change based on Google's policies). Next, the organization creates its own Netlify and Firebase accounts, choosing a plan based on what the app will need. If deploys under the chosen plan ever run out, the organization will be asked to upgrade its Netlify plan — and the same applies to Firebase, if the app handles a lot of photos or needs more storage. The full step-by-step for each of these is further down on this page.
  2. Ideas are exchanged by email (info@lnrcs.com) about the company's needs, the type of app you want, and the payment methods to be used — possibly over a few back-and-forth messages.
  3. If both sides agree, the service agreement is sent.
  4. You print it, sign it with your full name, date, and contact details, and email it to info@lnrcs.com along with a photo or scan of a government ID (front and back).
  5. The initial 50% is paid, and work begins.
  6. You invite LNR Consulting Services LLC as an authorized user in Google Play Console, Netlify, and Firebase, and email (info@lnrcs.com) over any brand material you have (website, colors, fonts, general look and feel, information, photos, links, payment details if the app will handle payments, etc.).
  7. A first proposal is sent by email (info@lnrcs.com), with different visual templates and app icon options.
  8. You review it and request changes; a revised second proposal is sent — once approved, the project design is finalized.
  9. The app is built and tested internally.
  10. Google Play policies and a company privacy policy are drafted (a starting draft is provided, open to your corrections).
  11. Feedback is gathered by email (info@lnrcs.com) on what information should appear on the Google Play listing.
  12. The app is published, and checked for errors.
  13. The remaining 50% is due at launch. Within the first 14 days, any bugs are fixed free of charge.
  14. Monthly maintenance billing begins once the app is published on Google Play. Done — the app is live, with maintenance in place!
Google Play Account & D-U-N-S

About the D-U-N-S Number

Only if you want the app published under your organization's name — which is how we set up every project. Google Play has two account types: Personal and Organization. A D-U-N-S number (a free identifier issued by Dun & Bradstreet) is required only for the Organization type.

This is the account your business, church, or institution will own and control — not ours. It's what lets your app carry your name, keep its own review history, and stay fully yours if we ever stop working together.

Important: we don't start development until this account is fully approved by Google. That protects you from paying for work on an app that can't be published if the account approval falls through.
Step-by-Step Guide

D-U-N-S and Google Play Console Registration

  1. Check if you already have one. Search your organization's legal name at the Dun & Bradstreet D-U-N-S lookup tool. Many organizations already have a D-U-N-S number without realizing it.
  2. If not, request one for free. Apply directly through Dun & Bradstreet. The standard request has no cost and can take up to 30 business days — sometimes less.
  3. Get your details ready while you wait. Your organization's exact legal name, address, website (if you have one), and a government-issued ID for whoever will own the account.
  4. Start your Google Play Console signup. Go to the Play Console signup page and choose the "Organization" account type.
  5. Fill in your details and pay the one-time fee. Organization name, address, your D-U-N-S number, and the $25 USD one-time registration fee.
  6. Upload verification documents. Google may request formation documents and an ID for the account's authorized representative.
  7. Wait for Google's approval. This can take anywhere from a couple of days to a couple of weeks.
  8. Invite us as an authorized user. Once approved: Settings → Users & permissions → Invite new users → add our email → grant permissions to manage production releases.
Start this as early as possible — even before we've finalized your proposal. It's the slowest step in the whole process, and it runs on Google's timeline, not ours.
Hosting & Storage

Netlify and Firebase Registration

  1. Create a free account at Netlify using the organization's email.
  2. Choose a plan based on the project's needs — see Netlify's plans.
  3. Invite LNR Consulting Services LLC as a site collaborator, using only the contact email.
  4. Create a project at the Firebase Console using a Google account belonging to the organization.
  5. Choose the Spark (free) or Blaze (pay-as-you-go) plan — see Firebase pricing.
  6. Add LNR Consulting Services LLC as a user with Editor permissions.
Account Access

Account Access

None of the three platforms (Google Play Console, Netlify, or Firebase) ever involves sharing a username and password — doing so goes against each platform's policies and isn't safe. Instead, LNR Consulting Services LLC is added as an authorized user on each platform, using only a contact email.

The account holder remains the owner of all three accounts at all times, and can review the access granted, adjust permissions, or revoke them whenever needed. Usage limits, billing, and account standing belong to the account holder — if free-tier limits are ever exceeded (for example, extra Netlify deploys, or Firebase storage), their own payment method covers that, separately from the development fee.

For most basic apps, this never comes up: Netlify and Firebase's free tiers comfortably cover typical usage, and photos can often be hosted directly on the existing website instead of Firebase Storage.

Payment & Accepted Methods

How Payment Works

Development is billed in two parts: 50% when the service agreement is signed (this is also when you'll invite us into your Google Play Console), and 50% at launch, once the app is live on Google Play.

Monthly maintenance is billed separately, starting the month the app launches.

Accepted payment methods:

  • Argentine pesos via ALIAS, CVU, or CBU
  • US dollars via US bank transfer, CashApp, Zelle, or Venmo
  • Credit or debit card
  • Crypto, in USDT or USDC
What's Included

Features a Basic App Can Include

A basic app can combine any mix of these, within the 5-screen scope described in Pricing:

  • Informational screens
  • Photo gallery
  • Contact form
  • Simple payments (donations, dues)
  • Live streaming (YouTube embedded in the app)
  • Social media links
  • Events calendar (services, talks, retreats)
  • Location map (embedded Google Maps)
  • Direct WhatsApp button
  • Service hours — static content, rarely updated
  • Basic push notifications
  • Prayer/petition request form
  • FAQ / frequently asked questions
Not sure which of these fit your project, or need something not on this list? Tell us what you have in mind and we'll confirm whether it fits the standard price.
Design & Development

How Design and Development Works

We start with a mockup — a visual draft of the app — before any code is written, so you can see exactly how it will look. You get up to 2 rounds of revisions on that design to request changes.

Once you approve the design in writing, it's considered final, and we move on to building the app.

Changes requested after written approval are treated as new work — they're either quoted separately or handled through your monthly maintenance allowance once the app has launched.
Maintenance

What's Included in Monthly Maintenance

Apps can stop working whenever Google or Android changes something, or fail for other reasons — that's why ongoing maintenance matters. It also covers new ideas or features you'd like to add along the way.

  • Guaranteed compatibility with every Android update
  • Up to 10 change or update requests per month (text, photos, events, links, minor design tweaks)
  • Bug fixes
  • Direct email support

Requests are reviewed and completed on Fridays. Send them whenever you'd like during the week — they'll be handled in that Friday batch.

Extra Requests

Requests Beyond the Monthly Limit

Each additional request beyond the 10 included is $20 USD, also processed on Fridays. Unused requests don't roll over to the next month.

After Launch

Post-Launch Warranty

If an error shows up within the first 14 days after the app is published, we fix it at no additional charge, and it doesn't count against your monthly request allowance.

Contract

Written Contract

Yes. Every project begins only after a signed Service Agreement, which sets out the scope, pricing, and terms described on this page. No work begins, and no payment is requested, before that agreement is signed.

Timeline

Estimated Timeline

Development typically takes a few weeks from approved design to launch, though timelines vary by project size. The two steps outside our control — the D-U-N-S/Organization account approval and Google's own review before publishing — are usually the biggest variables, so starting the account process early makes the biggest difference in how fast the app goes live.

Cancellation

Maintenance Plan Cancellation

Yes. Either party can end the maintenance relationship with 30 days' written notice. The app stays live and published under your own account — canceling maintenance only means future Android updates, bug fixes, and change requests are no longer included.

See the Work

Examples of Previous Work

Yes — a portfolio of live, published apps is available at lnrcs.com, including property management, exam prep, and notary tools currently on Google Play.